The Cleanest Board vs the Scored One

The short version: tokenmaxxing.sh

tokenmaxxing.sh (by 851-labs) is the minimalist entry in the token-board category: install the CLI, sync your ccusage totals, appear on a public board ranked by spend or tokens across 7-day, 30-day, and all-time windows. No badges, no profiles, no extra machinery — just a clean table of who consumed the most. There is a real appeal in that simplicity.

SigRank reads the same telemetry and scores it. The headline metric, Υ = cache_read × output / input², separates the operator whose spend compounds from the one whose spend just accumulates. tokenmaxxing.sh is the honest counter; SigRank is the evaluation layer on top of it.

Not to be confused with tokenmaxxer, a different (gamified) product in the same category.

Feature comparison

Where minimalism ends

A spend board answers "who consumed the most?" accurately and without pretension — which is more than most leaderboards can say. What it cannot tell you is whether the consumption was good. Two operators with identical spend can sit ten-fold apart in output-per-input. The counter cannot see the gap because the counter only counts.

SigRank's Υ Yield makes the gap visible: cache reuse and output amplify the score while fresh input penalizes it quadratically. The operator who compounds cached context outranks the one who re-sends it every turn — same spend, different skill. tokenmaxxing.sh gives you the ledger; SigRank tells you what the ledger means.

From spend to yield

If your usage is already syncing, SigRank reads the same telemetry and adds the scoring layer:

npm install -g sigrank
sigrank enroll      # create your operator identity
sigrank submit      # reads logs, scores, signs, publishes

Or skip the CLI and paste your token counts into the /score calculator — Υ Yield, class tier, and compression ratio instantly.

Frequently asked questions

Is tokenmaxxing.sh a SigRank alternative?

It is a different take on the same data. tokenmaxxing.sh is deliberately minimalist — a clean leaderboard that ranks spend or tokens and nothing else. That restraint is its appeal: it ranks exactly what it says it ranks, with no scoring machinery in between. SigRank asks the follow-up question: did the spend compound into signal? If you want the simplest possible 'who burned the most' board, tokenmaxxing.sh is a good one. If you want to know who is efficient, that is the layer SigRank adds.

What does 'tokenmaxxing' mean?

Tokenmaxxing is the practice of maximizing AI token usage — the trend that turned API spend into a competitive leaderboard category. tokenmaxxing.sh (by 851-labs) is one minimalist implementation: an npm CLI that syncs your ccusage totals to a public spend/tokens board. Note that it is a different product from tokenmaxxer, the gamified streaks-and-badges tracker — two similarly-named tools in the same category. SigRank sits beside both as the efficiency layer: the same telemetry, but scored for yield instead of ranked by volume.

Is ranking by spend the same as ranking by skill?

No — and tokenmaxxing.sh does not claim it is. A spend board is honest about what it measures: who consumed the most. The gap appears when two operators spend the same and get different results. One reuses cached context and produces high output per input; the other re-sends context every turn. On a spend board they tie. On SigRank's Υ-ranked board the difference is the whole point. Spend measures participation; yield measures how well the spend was driven.

Can I use tokenmaxxing.sh and SigRank together?

Yes — the same local ccusage data feeds both. Keep your tokenmaxxing.sh entry for the spend board, and run `sigrank submit` to add your signed efficiency score to the SigRank leaderboard. Minimalist on one side, measured on the other.