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.
git 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-context-budget)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-context-budget"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-context-budget/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/kevinzai/commander/ccc-context-budget"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-context-budget.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.00039 | $0.00564 |
| Opus 5.5 | $0.00016 | $0.00226 |
| Sonnet 5.5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
ccc-context-budget 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-context-budget — gauge context, cut bloat
CC Commander · /ccc-context-budget · a usage gauge, the biggest consumers and the next action.
Usage
/ccc-context-budget # gauge plus top recommendations
/ccc-context-budget --verbose # full per-component breakdown
Arguments: $ARGUMENTS
What happens
- Load the
context-budgetskill (repo source: skills/context-budget/SKILL.md) and follow its five phases in order: Inventory, Classify, Visual Report, Recommendations, Quick Actions. If the skill is not installed, do the same phases inline: estimate tokens for the system prompt, loaded instructions (CLAUDE.md, rules), invoked skills, tool definitions, file reads and conversation turns. - Pass
--verbosethrough when it appears in$ARGUMENTS. - Use the window size of the session's model. Current Claude models have a 1M-token window; use a smaller size only when the user names one or the session reports one.
- Show the gauge and the zone from the table below. Label every figure as an estimate.
- End with the skill's Quick Actions block.
Zones
| Usage | Zone | Action |
|---|---|---|
| 0–50% | 🟢 Green | Continue normally |
| 50–70% | 🟡 Yellow | Monitor; plan a compact soon |
| 70–80% | Orange | Run /ccc-save-session, then /compact or start fresh |
| 80–90% | 🔴 Red | Run /ccc-save-session now |
| 90%+ | ⚠️ Danger | Stop new work; save the session and start a new one |
In Orange or above, ask with AskUserQuestion (Codex: a plain-text question):
- 🟢 Save the session now — runs
/ccc-save-sessionso nothing is lost - Compact in place — runs
/compact; older detail is summarized - Keep going — accept the risk of automatic compaction
Done when
The report shows the gauge, the zone, the top consumers and the Quick Actions block. If the user chose to save, the saved handoff file path is reported.
See also
/ccc-save-session (save state for resumption) · /ccc-resume-session (load it in a fresh context) · /compact (built-in history compression)
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.
- 5d ago Changed · +6 lines · +16 tokens per session 96e990c90b70
- 1mo ago First seen · 43 lines · 23 tokens per session scan A 297b6173216b
ccc-context-budget is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 564 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
context-stats
Display context window usage and token statistics.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
compact-context
A command that saves important project status and decisions, then creates a shorter summary of a long coding-agent conversation.
rnb
RNB — opens the RuvNet Brain Console (same console as /rnbc, /rvbc, /brain-console and /ruvnet-brain:configure — every spelling works). Your whole RuvNet stack on one page. Read-only until you click.
justone
Start a Just One Prompt Challenge — ship a runnable project from a single prompt.
thread
Persistent context threads for cross-session work that spans phases. Lighter than pause/resume.