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-forkgit 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-fork)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-fork"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-fork.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.00016 | $0.01165 |
| Opus 5 | $0.00008 | $0.00583 |
| Sonnet 5 | $0.00003 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
ccc-fork 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 yesterday.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore Fork
Split your current Claude Code session into parallel branches to explore multiple implementation approaches simultaneously. Try different solutions, compare results, and merge the best one back.
Usage
/branch # Fork current session into a new branch
/branch "try hooks approach" # Fork with a description
/branch list # Show all active forks
/branch merge <id> # Merge a fork back into main session
/branch discard <id> # Discard a fork
How It Works
Fork a Session
/branch "approach A: use context API"
Forked session.
Fork ID: fork-a1b2c3
Description: approach A: use context API
Base commit: abc1234
Branch: explore/fork-a1b2c3
You're now in the fork. Changes here don't affect the main session.
Use /branch return to go back to the main session.
Resume with --fork-session
# From the CLI, fork an existing session
claude --resume --fork-session
# This creates a new session with the full context of the previous one
# but on a new git branch, so changes are isolated
Explore Multiple Approaches
# Main session: working on state management
/branch "approach A: React Context"
# ... implement with Context API ...
# ... run tests ...
/branch return
/branch "approach B: Zustand"
# ... implement with Zustand ...
# ... run tests ...
/branch return
/branch "approach C: Jotai"
# ... implement with Jotai ...
# ... run tests ...
/branch return
/branch list
# fork-a1b2c3: approach A: React Context (3 commits, tests passing)
# fork-d4e5f6: approach B: Zustand (2 commits, tests passing)
# fork-g7h8i9: approach C: Jotai (4 commits, 1 test failing)
/branch merge fork-d4e5f6
# Merged "approach B: Zustand" into main session.
# Discarding other forks...
Use Cases
Architecture Exploration
Compare different architectural approaches before committing:
"I need to implement caching. Fork three approaches:
1. In-memory with Map
2. Redis
3. SQLite
Each fork: implement, benchmark, and report performance numbers.
I'll merge the winner."
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.
- yesterday First seen · 184 lines · 16 tokens per session scan A a3f15035bed1
ccc-fork is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,165 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-03.
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]".