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-statusgit 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.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.00014 | $0.00501 |
| Opus 5 | $0.00007 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
status-updates 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 today.
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
Status Updates — Progress Notification Manager
Managing status updates: {{input}}
Subcommands
/status-updates on
Enable status updates with current defaults:
- Set
CC_STATUS_UPDATES=1 - Auto-detect available MCP channels (Slack > Discord > Email > Console)
- Default interval: 30 minutes
- Default level: brief
- Confirm: "Status updates enabled — [channel] every [interval]m"
/status-updates off
Disable status updates:
- Set
CC_STATUS_UPDATES=0 - Clean up signal files:
rm -f /tmp/cc-status-*.signal - Confirm: "Status updates disabled"
/status-updates configure
Interactive configuration:
- Channel: Which MCP channel to use?
- Auto-detect available channels
- List options: Slack, Discord, Email, Console
- Let user pick
- Interval: How often? (default: 30 minutes)
- Options: 5, 10, 15, 30, 60 minutes
- Detail level: Brief or detailed?
- Brief: one-line summary
- Detailed: full phase breakdown with stats
- Apply settings and confirm
/status-updates now
Send an immediate status update:
- Read current session state from
/tmp/cc-status-{sessionId}.json - Generate update using current detail level
- Send via configured channel
- Show what was sent
/status-updates status
Show current configuration:
STATUS UPDATES: [ENABLED/DISABLED]
Channel: [auto/slack/discord/email]
Interval: [X] minutes
Level: [brief/detailed]
Last sent: [time ago or "never"]
Next due: [time from now]
Tool calls since last: [count]
Session duration: [Xm]
Output
STATUS UPDATES: {{action}}
Channel: [detected channel]
Interval: [minutes]
Level: [brief/detailed]
State: [ACTIVE/INACTIVE]
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.
- today First seen · 76 lines · 14 tokens per session scan A 700d7e37fc63
status-updates is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 501 once invoked, about $0.0001 per session on Opus 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
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]".