Loading rankings…
Loading rankings…
Usage flare vs yield signal
| Feature | SigRank | ccflare |
|---|---|---|
| What it measures | Cascade yield over time | Usage spikes and flares |
| What it tells you | How efficiently you compound signal | When you spiked |
| Leaderboard | Yes — ranked by Yield, class tiers | No |
| Platform coverage | Claude Code, Cursor, Copilot, Gemini, 15+ | Limited |
| MCP server | Yes | No |
| Privacy | Token counts only — never prompt content | Token counts only |
ccflare shows usage flare — spikes in token consumption. SigRank shows yield signal — efficiency over time. Flare is noise; yield is signal.
SigRank's Yield (Υ) metric measures the architecture of your token cascade — is signal compounding, or are tokens burned? That's the question ccflare can't answer.
ccflare shows usage flare — spikes in token consumption. SigRank shows yield signal — efficiency over time. Flare is noise; yield is signal. SigRank's Yield (Υ) = (cache_read × output) / input² measures cascade efficiency.
Yes. They're complementary. Use ccflare for its function, and run sigrank submit to publish your cascade score to the leaderboard.
Yield (Υ) = (cache_read × output) / input² — token-cascade efficiency from real sessions. Works across Claude, GPT, Gemini, Cursor, Copilot, and any AI coding tool.
Visit signalaf.com/score to enroll and submit your token telemetry. SigRank will compute your Yield, your rank, and your operator class. Token counts only — never prompt content, never code.
Stop watching flares. Start tracking yield.
Check my Yield