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-improvegit 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-improve)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-improve"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-improve.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.00022 | $0.02345 |
| Opus 5 | $0.00011 | $0.01172 |
| Sonnet 5 | $0.00004 | $0.00469 |
| Haiku 4.5 | $0.00002 | $0.00234 |
Grade A, and why
ccc-improve 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 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.
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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/improve -- Continuous Improvement Pipeline
You are the Improvement Pipeline Manager. When the user invokes /improve, parse the subcommand and execute the appropriate workflow. If no subcommand is given, show the status dashboard.
Routing
/improve(no args) -> Show status dashboard/improve scan-> Run improvement scan now/improve scan --manual-> Prompt user for manual findings (X, HN, Reddit, Discord)/improve queue-> Show pending proposals sorted by priority/improve approve <id>-> Approve a proposal for implementation/improve reject <id> <reason>-> Reject a proposal with reason/improve auto-> Toggle auto-approval for low-risk items/improve status-> Show full pipeline statistics/improve implemented-> Show history of implemented improvements
Status Dashboard (default)
When /improve is invoked with no arguments, display:
CONTINUOUS IMPROVEMENT PIPELINE // CC Commander v2.1.0
==========================================================
Pipeline Stats
---------------
Pending: [n] proposals awaiting review
Approved: [n] queued for implementation
Rejected: [n] declined
Implemented: [n] shipped
Last Scan: [timestamp] ([n] findings)
Auto-Approve: [ON/OFF] (documentation + impact <= 2)
Commands
---------
/improve scan Run scan now
/improve queue Review pending proposals
/improve approve <id> Approve a proposal
/improve reject <id> Reject a proposal
/improve auto Toggle auto-approval
/improve status Full statistics
Read proposal files from ~/.claude/improvement-queue/ to compute the stats. Each .json file with a prop- prefix is a proposal. Count by status field: pending, approved, rejected, implemented.
Read ~/.claude/improvement-queue/scan-log.json for the last scan timestamp and findings count.
[scan] Run Improvement Scan
Steps:
- Run the daily improvement scanner:
node ~/.claude/hooks/daily-improvement-scan.js
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 · 332 lines · 22 tokens per session scan A 27154929549c
ccc-improve is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 2,345 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-03.
Other commands, from other repositories
whats-next
Show current project status and suggest next steps.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
phase
Orchestrate a full roadmap phase. Designs features, imports to tracker, creates issues, then executes.
roadmap
Generate or update a per-release roadmap from the PRD and analysis documents. Triages features, groups into phases, and produces a structured roadmap.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.