Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/citedy/skillsnpx agentmods add commands/citedy/skills/token-usageWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/citedy/skills/token-usage)<a href="https://agentmods.dev/commands/citedy/skills/token-usage"><img src="https://agentmods.dev/badge/commands/citedy/skills/token-usage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/citedy/skills/token-usage"><img src="https://agentmods.dev/badge/commands/citedy/skills/token-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00008 | $0.00151 |
| Opus 5.5 | $0.00003 | $0.00060 |
| Sonnet 5.5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
token-usage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Run the token usage analyzer with the provided arguments.
$ARGUMENTS can be: today, week, month, a number of days (e.g. 3), a date (2026-04-01), or empty for all time.
python3 .claude/skills/token-usage/scripts/analyze.py $ARGUMENTS
After running, read the output and present a concise summary to the user:
- Grand totals (tokens + estimated cost)
- Per-project breakdown
- Top 3 costliest sessions
The full report is saved to ~/.claude/token-usage-reports/token_report.md.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 18 lines · 8 tokens per session scan A 9c9b0397cc33
token-usage is a command published in the GitHub repository citedy/skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 151 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
earnings
Post-earnings analysis for a stock — fast in-chat summary card by default, full Markdown research report on request.
burn-rate
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
unit-economics
../../vertical-plugins/business-intelligence/commands/unit-economics.md.
competitive
../../vertical-plugins/equity-research-core/commands/competitive.md.
sector-overview
../../vertical-plugins/industry-analysis/commands/sector-overview.md.