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-makeovergit 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-makeover)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-makeover"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-makeover.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.00017 | $0.00354 |
| Opus 5 | $0.00009 | $0.00177 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
ccc-makeover 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
/ccc-makeover
Automatically apply the highest-impact recommendations from an X-Ray scan.
What It Does
- Runs
/ccc-xrayto get current health score and recommendations - Presents the top 5 recommendations sorted by impact
- For each recommendation, offers to:
- Run the recommended skill automatically
- Skip to the next recommendation
- Stop the makeover
- Tracks improvements: shows before/after health score
Usage
/ccc-makeover
Options
--dry-run-- show recommendations without applying--auto-- apply all recommendations without prompting--max N-- limit to N recommendations (default: 5)--category CAT-- focus on one dimension (security, testing, devops, quality, docs, architecture)
Example Flow
Current Health: 42/100 (Maturity: 2 - Managed)
[1/5] No CLAUDE.md (impact: 80)
-> Running /project-kickoff...
-> Done. CLAUDE.md created.
[2/5] No test files (impact: 90)
-> Running /tdd-workflow...
-> Done. 12 test files created.
[3/5] No CI pipeline (impact: 85)
-> Running /senior-devops...
-> Done. .github/workflows/ci.yml created.
Updated Health: 71/100 (Maturity: 3 - Defined)
Improvement: +29 points
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 · 53 lines · 17 tokens per session scan A a2aaacebab81
ccc-makeover is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 354 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
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.