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-multi-repo)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-multi-repo"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-multi-repo/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-multi-repo"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-multi-repo.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.00048 | $0.01300 |
| Opus 5.5 | $0.00019 | $0.00520 |
| Sonnet 5.5 | $0.00010 | $0.00260 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
ccc-multi-repo 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 8d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-multi-repo — one change, several repos
CC Commander · /ccc-multi-repo · coordinated edits, branches and checks across every repository in the session.
Usage
/ccc-multi-repo # guided setup for a cross-repo change
/ccc-multi-repo add <path> # add a repository to this session
/ccc-multi-repo status # branch and working state of every repo
/ccc-multi-repo verify # run each repo's checks and report
Arguments: $ARGUMENTS. With no subcommand, run the guided setup.
Adding repositories
Start a session with extra repositories:
cd ~/projects/api-server
claude --add-dir ~/projects/web-client --add-dir ~/projects/mobile-app
Inside a running session, the user adds one with the built-in /add-dir <path>. For /ccc-multi-repo add <path>:
- Check the path is a git repository:
git -C <path> rev-parse --show-toplevel. On failure, report it and stop. - Tell the user to run
/add-dir <path>(the assistant cannot type built-in slash commands), then confirm access by reading a file from it. - Run
statusto show the new set.
Added directories support reading, editing and creating files, running shell commands and tests in that directory, installing dependencies, and git operations (each repo keeps its own git). --add-dir does not merge git histories, create symlinks, share node_modules, or change the other repo's .claude/settings.json.
Refer to files by absolute path (~/projects/web-client/src/types.ts) or name the repo first ("in web-client, read src/types.ts").
Status
For the primary working directory and every added directory:
git -C <repo> rev-parse --show-toplevel
git -C <repo> branch --show-current
git -C <repo> status --short
Report one row per repo: path, primary or added, branch, clean or the count of changed files.
Guided setup
- Ask the user for the change and the repos it touches, or read it from
$ARGUMENTS. - Run
status. If any repo has uncommitted changes, report them and do not overwrite them. - Order the repos by dependency: shared types and schemas first, then services, then clients. Start editing in the most foundational repo.
- Before creating branches, ask with AskUserQuestion (Codex: a plain-text question):
- 🟢 Same branch everywhere — create
feat/<name>in each repo withgit -C <repo> checkout -b feat/<name> - Use existing branches — work on each repo's current branch
- Cancel — stop without changes
- 🟢 Same branch everywhere — create
- Make the change repo by repo, keeping each repo's edits to its part of the contract.
- Run
verify.
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.
- 8d ago Changed · -118 lines · +34 tokens per session 8af51adc808e
- 1mo ago First seen · 229 lines · 14 tokens per session scan A 209eaba835f1
ccc-multi-repo is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,300 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
justone-publish
Publish a completed JustOne build — create a public GitHub repo, push, and register on the gallery.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
commit
Split the changes into atomic commits, preflight and push them. Pass --skip-preflight or --no-push to skip a step.
doc-changelog
Generation and maintenance of the project changelog.
ops-gitflow
Manage the GitFlow branching model: init, feature, release and hotfix branches.
fix-issue
A command that takes a GitHub Issue—a tracked bug, request, or question—and guides its fix from investigation through testing and submission. TDD means writing a failing test first, then changing the code until the test passes.