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-refreshgit 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-refresh)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-refresh"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-refresh.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.00027 | $0.01095 |
| Opus 5 | $0.00014 | $0.00548 |
| Sonnet 5 | $0.00005 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
ccc-refresh 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-refresh — Deprecated Alias
⚠️ Deprecated in v4.0.0-beta.1. Use
/ccc-init— unified init + refresh that auto-detects whether to scaffold or merge-refresh.
This alias is preserved for backward compatibility and will be removed in v5.0. The execution behavior below is identical to the refresh path in /ccc-init.
This command analyzes your existing CLAUDE.md and proposes updates based on the latest CC Commander template.
What This Command Does
- Reads your current
~/.claude/CLAUDE.md(or project-level CLAUDE.md) - Compares H2 sections against the latest CC Commander v2.1.0 template
- Identifies: missing sections, outdated sections, custom sections
- Proposes a merge plan showing what would be added/updated
- Preserves all custom sections you've written
- Applies changes only after your explicit confirmation
Merge Strategy
- Missing sections: Added from template with
<!-- Added by CC Commander v2.1.0 -->marker - Outdated sections: Template version shown side-by-side for comparison
- Custom sections: Left untouched (any H2 not in template is considered custom)
- User name: Preserved from existing file (not overwritten with placeholder)
When to Use
- After upgrading CC Commander
- When your CLAUDE.md is >30 days old
- When CCC staleness hook suggests a refresh
- After running /makeover on a project
- Periodically to pick up new best practices
Auto-Prompt Triggers
The claude-md-staleness hook will suggest running this command when:
- CLAUDE.md is missing entirely
- Template version is older than installed CC Commander version
- File hasn't been modified in >30 days
- Key H2 sections are missing (Workflow, Core Principles, etc.)
Execution Steps
When invoked, follow this procedure:
Step 1: Read Current State
Read the user's CLAUDE.md. Extract:
- The HTML version comment (if any) at the top of the file
- All H2 (
##) section headers and their content - The user's name from the H1 title line
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 · 126 lines · 27 tokens per session scan A 63749ea5d092
ccc-refresh is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,095 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]".