tokenaires
Star1

How it works

One command signs you in with GitHub, reads the usage logs your agents already keep, and sends token counts. Nothing else.

Example run

$

Example: running npx tokenaires signs you in with GitHub, scans Claude Code and Codex logs, uploads token counts and shows your rank.

  1. 1

    Sign in with GitHub

    • The CLI shows a short code and opens github.com/login/device. Enter the code and approve.
    • Your public GitHub profile becomes your name, handle and avatar on the list.
    • The GitHub token is used once to read your profile and is never stored.
  2. 2

    What gets read

    • Claude Code session logs in ~/.claude/projects.
    • Codex session logs in ~/.codex/sessions.
    • Only the token counts, model name, time and message ID from each response.
  3. 3

    What gets sent

    • Per message: tool, message ID, model, time, and input, output and cache token counts.
    • Never prompts, replies, code, file paths, project names or branch names.
    • Run npx tokenaires scan to see your totals locally before you send anything.
  4. 4

    How the list stays honest

    • The server adds up every total. The CLI only sends raw records.
    • Every message ID can belong to one account. Copy someone else's logs and both accounts get flagged.
    • Uploads are signed by a key that lives on your machine, and each signature works once.
    • Records from the future, from before a tool or model existed, or with impossible token counts are refused.
    • Unusual spikes put a profile under review. It stays on the list with a marker until it is checked.
  5. 5

    Ranking

    • Net worth is input, output, cache reads and cache writes added together.
    • All time, 30 days and 7 days boards, filtered by tool.
    • Movement shows how far you climbed on the all time board this week.
    • Tiers: Thousandaire at 1K, Millionaire at 1M, Billionaire at 1B, Trillionaire at 1T.