Early access — cascade metrics are real (derived from canonical token telemetry); the operator field is a curated seed. Learn more about the data
\u25C8 SigRank vs ccgather

Claude Code Only Isn't the Whole Field.

ccgather ranks Claude Code users by usage stats. SigRank ranks operators by cascade yield across 15+ platforms. One tool is not the whole field.

The short version: ccgather

ccgather is a leaderboard for Claude Code users. It gathers usage stats — how much you used Claude Code — and ranks users by them. It does its job: it ranks the Claude Code crowd. But most operators don't use just one tool. They drive Claude Code for some tasks, Cursor for others, Copilot for others. A Claude Code-only leaderboard misses everyone who isn't on Claude Code and can't compare operators across platforms.

SigRank is platform-neutral. It reads telemetry from Claude Code, Cursor, Copilot, Gemini, and 15+ other tools, scores the cascade yield, and ranks every operator on the same scale. The headline metric, Υ Yield = cache_read × output / input², rewards the operator who reuses cached context efficiently — no matter which tool they drove. ccgather ranks the Claude Code crowd; SigRank ranks the whole field.

Feature comparison

FeatureccgatherSigRank
What it ranksClaude Code usage statsOperator cascade yield (Υ = cache_read × output / input²)
Platform coverageClaude Code onlyClaude Code, Cursor, Copilot, Gemini, 15+ platforms
Cascade efficiency score (Υ Yield)NoYes
Compression ratio + SNR + Leverage + VelocityNo (usage stats)Yes (derived metrics)
Class tier (IGNITER to ARCH+)NoYes
Operator profiles + head-to-head comparePartial (leaderboard profiles)Yes
MCP server for AI-agent integrationNoYes
ed25519-signed snapshot submissionNoYes
Bundled tools (tokscale, token-dashboard)NoYes
Privacy-preserving (token counts only)YesYes

Why one tool isn't the whole field

ccgather answers "who used Claude Code the most?" That's a useful question, but it's not the whole question. Most operators don't use just one tool. They drive Claude Code for some tasks, Cursor for others, Copilot for others. A Claude Code-only leaderboard can't compare an operator who uses Cursor 80% of the time with one who uses Claude Code 80% of the time. It can't see the operator who is most efficient across all platforms.

SigRank's headline metric, Υ = cache_read × output / input², is platform-neutral. It reads the same four token pillars from every supported tool and scores the cascade yield on the same scale. ccgather ranks the Claude Code crowd; SigRank ranks the whole field.

The four token pillars (both tools read these from Claude Code)

  • Input: tokens you send to the model
  • Output: tokens the model generates back
  • Cache-read: cached tokens reused from prior context
  • Cache-write: new tokens written to cache for future reuse

From Claude Code to the whole field

If you already run ccgather, you have the Claude Code stats. SigRank reads the same telemetry and adds the cross-platform scoring layer Claude Code-only leaderboards never had:

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

Prefer to inspect before you submit? Run sigrank me --dry-run to see your scored payload locally, or paste your token counts into the /score calculator to compute your Υ Yield, class tier, and compression ratio instantly, no account, no submission, just the numbers.

Frequently asked questions

Is SigRank a ccgather alternative?
They overlap on having a leaderboard but diverge on scope and scoring. ccgather ranks Claude Code users by usage stats — how much you used Claude Code. SigRank ranks operators by cascade yield across 15+ platforms. If you want a Claude Code-only usage leaderboard, ccgather is that. If you want to know who is the most efficient AI operator across every platform, SigRank answers that. You can run both — they read the same Claude Code logs.
Why is Claude Code-only not enough?
Most operators don't use just one tool. They drive Claude Code for some tasks, Cursor for others, Copilot for others. A Claude Code-only leaderboard misses everyone who isn't on Claude Code and can't compare operators across platforms. SigRank is platform-neutral: it reads telemetry from Claude Code, Cursor, Copilot, Gemini, and 15+ other tools, scores the cascade yield, and ranks every operator on the same scale. One tool is not the whole field.
What does ccgather not measure that SigRank does?
ccgather reports Claude Code usage stats and ranks by them. SigRank reads the same four token pillars and derives the cascade architecture: Υ Yield (is signal compounding or burning?), compression ratio (output per input), SNR (signal density), Leverage (how much cached context amplifies your input), and Velocity (tokens per unit time). ccgather tells you who used Claude Code the most; SigRank tells you who is the most efficient operator across every platform.
Can I use both ccgather and SigRank?
Yes. ccgather gives you the Claude Code usage leaderboard. SigRank gives you the cross-platform yield ranking. Run `sigrank submit` to publish your cascade score to the SigRank leaderboard, and keep ccgather for the Claude Code crowd. The two are complementary, not mutually exclusive. The same local logs feed both.
Which is better for comparing operators across platforms?
SigRank. ccgather can only compare operators who use Claude Code. SigRank compares operators across Claude Code, Cursor, Copilot, Gemini, and 15+ other platforms on the same yield scale. If you want to know who is the best AI operator — not just the best Claude Code user — you need a platform-neutral ranking. ccgather is Claude Code only; SigRank is the whole field.

Ready to see your yield?

Keep your Claude Code leaderboard for the ccgather crowd. Add the cross-platform yield ranking that Claude Code-only leaderboards cannot provide. Install SigRank and submit your first signed snapshot in under a minute.

Related: ccusage Alternatives · Yield Calculator · The Local Agent (MCP)