Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/centminmod/my-claude-code-setup/ccusage-dailygit clone --depth 1 https://github.com/centminmod/my-claude-code-setupWhat 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 | $0.00000 | $0.00493 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
ccusage-daily 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 3d 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
Please run the ccusage daily -b command and then provide a structured markdown summary of the Claude Code usage costs and statistics.
Required Actions:
- Execute
ccusage daily -busing the Bash tool - Parse the output to extract key metrics and statistics
- Generate a comprehensive markdown report
Report Format Required:
Executive Summary
- Total cost for the period
- Date range covered
- Number of usage days
- Average daily cost for sonnet
- Average daily cost for opus
- Average daily cost for sonnet + opus
- Peak usage day and cost for sonnet
- Peak usage day and cost for opus
- Peak usage day and cost for sonnet + opus
- Cache efficiency percentage
Key Statistics Table
A markdown table with usage broken down by model and model totals:
- Total Tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Input Tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Output Tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Cache Read Tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Total Cost
- Average Daily Cost
Daily Cost Summary Table
A compact markdown table showing:
- Date (in MM-DD format)
- Model used
- Input tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Output tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Cache read tokens (in millions i.e. 1,234,567 reported as 1.2345 m)
- Total cost for that day
Limit to the top 15-20 highest cost days to keep the table manageable.
Usage Insights
Provide analysis including:
- Number of high usage days (over $20)
- Cache effectiveness assessment
- Token distribution breakdown
- Primary model identification
- Usage patterns and trends
Recommendations
Based on the data, provide:
- Cost management insights
- Cache optimization observations
- Usage pattern analysis
Please format everything in clean, readable markdown with proper tables and bullet points. Focus on actionable insights and clear presentation of the cost and usage data.
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.
- 3d ago First seen · 56 lines · 0 tokens per session scan A 75422eef166b
ccusage-daily is a command published in the GitHub repository centminmod/my-claude-code-setup (2,614 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 493 tokens. 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-30.
Other commands, from other repositories
sp.reverse-engineer
Reverse engineer a codebase into SDD-RI artifacts (spec, plan, tasks, intelligence).
sp.checklist
Generate a custom checklist for the current feature based on user requirements.
sp.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
sp.specify
Create or update the feature specification from a natural language feature description.
sp.git.commit_pr
An autonomous Git agent that intelligently executes git workflows. Your task is to intelligently executes git workflows to commit the work and create PR.
sp.adr
Review planning artifacts for architecturally significant decisions and create ADRs.