Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for power users and teams that want to see token burn and quota pressure before AI coding costs sprawl into guesswork.
Who should use it
Who should skip it
Skip stormzhang/token-tracker unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
stormzhang/token-tracker is tracked by RepoRadar as a token cost tracker in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for stormzhang/token-tracker are workflow potential (9.7) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned stormzhang/token-tracker a composite score of 8.2 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 4.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It writes local statusline and hook configuration for agent CLIs, so inspect the generated setup before enabling it on machines with custom wrappers or shell workflows.