BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

token-tracker

Skill Development Usable
Works inClaude Code
Usable Scanned — metadata only

Tracks token consumption across AI coding assistants in real time, exposing hidden usage costs and preventing budget overruns in high-volume development envi…

Claude Code & Codex 本地 token 追踪 — 状态栏(Codex 业界首创伪 statusline)、GitHub 风格热力图、多模型成本分析。 | Local token tracker for Claude Code & Codex — status line (industry-first Codex faux statusline), GitHub-style heatmap, multi-model cost analysis

462 starsMIT (commercial OK)FreeQuick setup
Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Tracks token consumption across AI coding assistants in real time, exposing hidden usage costs and preventing budget overruns in high-volume development environments.

Engineering teams using Claude or Codex extensively who need visibility into per-developer token spend and cost allocation.

Claude Code Claude Cowork Claude Chat

https://github.com/stormzhang/token-tracker

By stormzhang

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → PluginsAdd plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
claude plugins install stormzhang/token-tracker

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me track token usage across Claude models in real-time during development sessions
CostFree

Trust Signals Auto-scanned

Stars462Last updated2026-08-01LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-01 · scanner v1

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 462 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

  • Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
3/5
Versatility
4/5
Reliability
3/5
Security
3/5
Overall score3.25 / 5.00 UsableEvaluatedAug 2026
Scored from trust signals (evidence-eval-v1): 462 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →