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-makeover)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-makeover"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-makeover/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-makeover"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-makeover.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.00047 | $0.01078 |
| Opus 5.5 | $0.00019 | $0.00431 |
| Sonnet 5.5 | $0.00009 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
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 6d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-makeover — fix the top X-Ray findings
CC Commander · /ccc-makeover · baseline score, approved fixes in impact order, and a re-scored before/after.
Usage
/ccc-makeover [--dry-run] [--auto] [--max N] [--category CAT]
$ARGUMENTS:
--dry-run— list the recommendations and stop; nothing changes--auto— apply every target without the per-target picker (only when passed in this request)--max N— at most N targets (default 5)--category CAT— one dimension:security,testing,devops,quality,docsorarchitecture
What happens
-
Baseline. Run
/ccc-xray. With thecccCLI installed, take the numbers from its scorer so the before and after use the same rubric:CCC_ROOT="$(cd "$(dirname "$(realpath "$(command -v ccc)")")/.." && pwd)" node -e 'const x=require(process.argv[1]+"/commander/xray-report").generateReport(process.cwd());console.log(JSON.stringify({overall:x.health.overall,dimensions:x.health.dimensions,maturity:x.maturity,recs:x.recommendations.map(r=>({skill:r.skill,category:r.category,score:r.score,explanation:r.explanation}))}))' "$CCC_ROOT"Record the overall score, each dimension score and the maturity level. If neither the scorer nor
/ccc-xrayproduces a scorecard, stop and report why. -
Pick targets. Sort recommendations by impact score, highest first. Keep only
--categorywhen given, then at most--max N. Show them:Current health: 42/100 (maturity 2 · Managed) [1/5] No test files (impact 90) -> /ccc-tdd [2/5] No CI pipeline (impact 85) -> ccc-devops [3/5] No CLAUDE.md (impact 80) -> project-kickoffIf a recommended skill is not installed here, name the closest installed command (for example
/ccc-tddfor missing tests) and say so. With--dry-run, stop here. -
Apply, one at a time. Unless
--autowas passed, ask for each target with AskUserQuestion (plain-text question where unavailable):- 🟢 Apply — run the recommended skill or command for this target
- Skip — move to the next target
- Stop — end the makeover and go to step 5
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.
- 6d ago Changed · +26 lines · +30 tokens per session 631f6623ae48
- 1mo ago 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 47 tokens to every session and 1,078 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
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.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.