tokenmaxxing CLI
A CLI built on ccusage that syncs your daily agent token usage to a public profile and leaderboard on tokenmaxxing.sh
- 90 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI sends daily usage totals from agent logs to an external server and makes the profile public.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/tokenmaxxingDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI sends daily usage totals from agent logs to an external server and makes the profile public.
This is third-party code. Review the repository files before installing.
What it does
tokenmaxxing reads local coding agent logs through ccusage, computes daily token totals and API-equivalent spend and sends those aggregates to your public profile. On tokenmaxxing.sh they are compared over a week, a month and all time. Sync is idempotent, and profiles merge data from several devices. The `tokenmaxxing bootstrap` command signs in, sends what has accumulated, optionally enables automatic sync and opens the profile. After that `tokenmaxxing sync` works with `--dry-run`, `--since` and `--sources`, and `tokenmaxxing service install` starts background sync every five minutes. Claude Code, Codex, OpenCode, Gemini CLI, Copilot CLI, Hermes, Amp, Qwen Code, Kimi CLI, Goose, OpenClaw and others are supported.
Who it is for. Users of Claude Code, Codex and other agents who want to compare their token usage with others and keep a public profile.
Good fit when
- You want daily token usage and its dollar equivalent on one page
- Data from a laptop and a work machine should combine in one profile
- Before sending you want to see exactly what will go out with `tokenmaxxing sync --dry-run`
- Only selected agents should be reported, using `--sources claude,codex`
Not a fit when
- Usage data must stay private, while the profile and leaderboard are public
- You need local cost tracking with no account or cloud, and ccusage alone fits that
- You need the exact provider invoice amount, while this reports an API-equivalent estimate
Example request
Show with `tokenmaxxing sync --dry-run` which of my token usage data would be sent to the serverLimitations
An account on tokenmaxxing.sh is required: `bootstrap` signs in and opens the public profile. Daily token aggregates and API-equivalent spend go to the server without conversation text, but the profile is visible to everyone. The background service runs on macOS, Linux and Windows and updates through the package manager that installed the CLI. Non-default log paths are set with variables such as `CODEX_HOME` and `GROK_HOME`.
How to disable. Run `tokenmaxxing logout` to revoke the device token, then remove the service with the `tokenmaxxing service` command and the package with `npm uninstall -g @851-labs/tokenmaxxing`.
FAQ
How do I install tokenmaxxing?
Run `npm install -g @851-labs/tokenmaxxing@latest`, then `tokenmaxxing bootstrap`, which signs in, syncs accumulated data and opens your profile.
What exactly is sent to the server?
Daily token totals and API-equivalent spend. `tokenmaxxing sync --dry-run` shows the exact payload before sending.
Can I turn off automatic sync?
Yes: the service is installed separately with `tokenmaxxing service install`, and `tokenmaxxing service status` shows its state. Without the service, sync runs only on `sync`.
How does tokenmaxxing differ from ccusage?
ccusage counts usage locally, while tokenmaxxing takes its data and publishes it to a public profile with a leaderboard.
Which agents are supported?
Claude Code, Codex, OpenCode, Gemini CLI, Copilot CLI, Hermes, Pi, Amp, Qwen Code, Kimi CLI, Kilo Code, Goose, Droid, Codebuff, OpenClaw and more. The `--sources` flag narrows the set.
Discussion
No questions or reviews yet.
Related
CLI toolsToken and cost reports for Claude Code, Codex, Gemini CLI and other agents from local logs, by day, month and session
TokenTracker counts tokens and spend across Claude Code, Codex, Cursor, Gemini CLI and other agents from local logs and shows them on a local dashboard
Tokdash shows token usage and session cost for Claude Code, Codex, Gemini CLI and a dozen more agents locally
A desktop widget with quota balances and token use across Claude, Codex, Kimi, GLM and other agents in one window.
Counts token use and cost of Claude Code and Codex sessions from local logs and shows remaining limits in the status line
A CLI and local dashboard that find token overspend in Claude Code and Codex sessions and suggest concrete fixes
README in short
The README gives a two-command install, explains how it works on top of ccusage, lists about twenty supported agents, the `sync` and `service` commands and variables for non-default log paths.