Tokenmaxxing

tokenmaxxing.sh

    The best place to track token usage
    A local CLI, built on ccusage, that syncs your token usage with everyone else.

Installation

bootstrap signs you in, syncs the usage already on your machine, optionally
installs automatic syncing, and opens your public profile.

How it works

tokenmaxxing uses ccusage to read local coding-agent
usage, turn it into daily token and API-equivalent spend totals, and sync those
aggregates to your public profile. The leaderboard lets you compare spend or
tokens over the last 7 days, 30 days, or all time.

Sync is idempotent and profiles aggregate across devices, so you can run
tokenmaxxing bootstrap on every machine and sync as often as you like.

Supported agents

- Claude Code
- OpenAI Codex
- OpenCode
- Gemini CLI
- GitHub Copilot CLI
- Hermes
- Pi
- Oh My Pi
- Grok Build CLI
- Antigravity
- ZCode
- Amp
- Qwen Code
- Kimi CLI
- Kilo Code
- Goose
- Droid
- Codebuff
- OpenClaw

Agents stored outside their default location are found through the same
environment variables ccusage reads (for example CODEX_HOME, GROK_HOME, or
AMP_DATA_DIR; see ccusage's
environment variables).

Oh My Pi is read with ccusage's Pi parser, pointed at OMP's own sessions:
~/.omp/agent/sessions and every named profile under ~/.omp/profiles/,
following PI_CONFIG_DIR and an existing $XDG_DATA_HOME/omp like OMP does.
Pi and Oh My Pi never count each other's sessions: OMP ignores PI_AGENT_DIR,
and Pi skips any PI_AGENT_DIR entry that points at OMP's sessions.

Usage

The background service supports macOS, Linux, and Windows. It uses the global
tokenmaxxing binary and keeps itself current through the package manager that
installed the CLI when that package manager can be detected.

Custom agent log roots (CLAUDE_CONFIG_DIR, CODEX_HOME,…