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/kevinzai/commander/ccc-costgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-cost)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-cost"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-cost.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00325 |
| Opus 5 | $0.00004 | $0.00162 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
ccc-cost scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Run: `curl -s http://localhost:3005/api/costs` What it actually says
/cost — Cost Tracker
Agent HQ API at localhost:3005. Shows spending across all Claude sessions.
When activated:
Run: curl -s http://localhost:3005/api/costs
Parse the JSON and display:
Cost Dashboard
═══════════════════════════════
Today: $[today] ([todayTokens] tokens)
Yesterday: $[yesterday] ([yesterdayTokens] tokens)
Total: $[total] ([totalTokens] tokens)
By Agent:
[agent1] $[cost] [██████████░░░░░░] [messages] msgs
[agent2] $[cost] [████░░░░░░░░░░░░] [messages] msgs
...
Then present via AskUserQuestion:
| Option | What it does |
|---|---|
| View daily breakdown (Recommended) | Show cost per day for last 7 days |
| View by agent | Show cost per agent with message counts |
| View by model | Group costs by model (opus/sonnet/haiku/flash) |
| Set budget alert | Ask threshold, save to state |
| Something else | Free text |
Budget Alert
If daily cost > $5, show warning:
⚠️ Daily spend: $[amount] (threshold: $5.00)
After every action, suggest next steps via AskUserQuestion.
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.
- yesterday First seen · 45 lines · 8 tokens per session scan A 9b1ab8e80783
ccc-cost is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 325 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
review
Run a Codex code review of your working tree or a branch (read-only).
adv-codex
Send a prompt to Codex CLI and return the response.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
add-hook
Add a new hook to .claude/settings.json. Quick operation, no full interview needed. Trigger phrases: "add hook", "auto-format on save", "run tests after edit", "lint on write", "run [command] after [tool]".