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-init)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-init"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-init/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-init"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-init.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.00052 | $0.01076 |
| Opus 5.5 | $0.00021 | $0.00430 |
| Sonnet 5.5 | $0.00010 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade B, and why
ccc-init scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
8. Verify: `head -1 CLAUDE.md`, `ls tasks/ .claude/settings.json`, and `git diff --stat` inside git. Confirm `.claude/settings.json` parses with `node -e "JSON.parse(require('fs').readFileSync('.claude/settings.json'))"` How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-init — project init and refresh
CC Commander · /ccc-init · one command that scaffolds a new project or merge-refreshes an existing CLAUDE.md, applied only after you approve the plan.
/ccc-refresh is a deprecated alias for the refresh path of this command.
What happens
-
Locate the template:
CLAUDE.md.templateat the root of the CC Commander install or checkout. Read the installed version from that install'spackage.json(node -p "require('./package.json').version"run in that directory). If the template is not found, ask the user for its path and stop until it is given. -
Detect the project state from the repository root (
git rev-parse --show-toplevel, or the current directory outside git):- No
CLAUDE.md→ scaffold. CLAUDE.mdunmodified for more than 30 days (date -r CLAUDE.md), or its header comment records a version different from the installed one → refresh.- Otherwise → report healthy and offer the optional template sections it lacks.
- No
-
Check the companions:
tasks/,tasks/todo.md,tasks/lessons.md,.claude/settings.json. -
Build the merge plan:
- Scaffold: the full layout below.
- Refresh: compare H2 sections of
CLAUDE.mdwith the template:- MATCH — header in both, bodies equal → keep
- UPDATE — header in both, bodies differ → side-by-side proposal
- MISSING — in the template only → add, marked
<!-- Added by CC Commander <installed version> --> - CUSTOM — in the user's file only → preserved untouched
- Preserve the user's name and every filled-in placeholder; never reintroduce
[placeholder]text over real content.
-
Show the plan:
# Project Initialization ## State detected - CLAUDE.md: present, header <recorded version> → <installed version> available - tasks/lessons.md: missing - .claude/settings.json: missing - Last modified: <n> days ago ## Proposed actions + [SCAFFOLD] tasks/lessons.md + [SCAFFOLD] .claude/settings.json (project permissions scaffold) ~ [REFRESH] CLAUDE.md — <n> new H2 sections, <n> updated = [KEEP] "My Custom Rules" section (untouched)
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 · +3 lines · +20 tokens per session scan A → B aef91fe255b3
- 1mo ago First seen · 81 lines · 32 tokens per session scan A f85fb2d658ce
ccc-init is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,076 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.