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-status)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-status"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-status/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-status"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-status.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.00056 | $0.01065 |
| Opus 5.5 | $0.00022 | $0.00426 |
| Sonnet 5.5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
ccc-status 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-status — progress updates while you are away
CC Commander · /ccc-status · periodic status messages from a long-running session to the channel you choose.
Subcommand: $ARGUMENTS (default status).
How it works
The hooks/status-reporter.js PostToolUse hook counts tool calls and, when the interval has elapsed, writes a signal file. The status-updates skill then composes and sends the update. The hook reads its settings from its environment:
| Variable | Default | Meaning |
|---|---|---|
CC_STATUS_UPDATES |
0 |
1 enables reporting |
CC_STATUS_INTERVAL |
30 |
Minutes between reports |
CC_STATUS_CHANNEL |
auto |
slack, discord, email or auto |
CC_STATUS_LEVEL |
brief |
brief (one line) or detailed (phase breakdown with stats) |
State lives in ${TMPDIR:-/tmp}/cc-status-<sessionId>.json; the signal file is ${TMPDIR:-/tmp}/cc-status-<sessionId>.signal.
A session cannot change its own hook environment. Settings take effect when they are in the env block of .claude/settings.local.json (or exported before launch) and a new session starts.
Channels are optional connectors, absent by default. Detect them from the tools exposed in this session, in this order: Slack, Discord, email (drafts only), then console as the fallback.
What happens
on
- Detect the available channel as above.
- Write
CC_STATUS_UPDATES=1,CC_STATUS_INTERVAL=30,CC_STATUS_LEVEL=briefand the detectedCC_STATUS_CHANNELinto theenvblock of.claude/settings.local.json, preserving every other key. - Verify by reading the file back, then report: "Status updates enabled — every m, from the next session."
off
-
Set
CC_STATUS_UPDATESto0in the sameenvblock and read it back. -
Remove this machine's leftover signal files:
rm -f "${TMPDIR:-/tmp}"/cc-status-*.signal -
Report "Status updates disabled."
configure
Ask with AskUserQuestion (Codex: a plain-text question), one question at a time:
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 · +20 lines · +42 tokens per session 7bb0f77410bd
- 1mo ago First seen · 76 lines · 14 tokens per session scan A 700d7e37fc63
ccc-status is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,065 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-04.
Other commands, from other repositories
on
Prevent the machine from sleeping (optionally for a fixed duration).
busy
Inhibit sleep only while Claude is actively processing.
context-stats
Display context window usage and token statistics.
cancel-ralph
Cancel active Ralph Wiggum loop.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.