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-parallelgit 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-parallel)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-parallel"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-parallel.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.00014 | $0.01385 |
| Opus 5 | $0.00007 | $0.00692 |
| Sonnet 5 | $0.00003 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
ccc-parallel 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Agents
Run multiple Claude Code instances simultaneously, each in its own git worktree, working on independent tasks. Merge results when all agents complete.
Usage
/parallel-agents # Interactive setup
/parallel-agents 3 "task prompt" # Launch 3 agents with same task
How It Works
Git Worktrees
Each agent gets its own git worktree -- a separate working directory that shares the same git history but has its own branch and file state.
# Claude Code creates worktrees automatically
claude -w # Launch in a new worktree
claude -w feat/auth # Launch in worktree on feat/auth branch
Parallel Execution
Main session (coordinator)
|
+--> Worktree 1 (agent-1): feat/add-auth
| Independent branch, full file access
|
+--> Worktree 2 (agent-2): feat/add-dashboard
| Independent branch, full file access
|
+--> Worktree 3 (agent-3): feat/add-api-tests
Independent branch, full file access
Each agent:
- Has its own branch
- Has its own working directory
- Can read/write files independently
- Cannot see other agents' uncommitted changes
- Runs its own tests and verification
Quick Start
Launch Parallel Agents
# Method 1: From the CLI
claude -w feat/auth &
claude -w feat/dashboard &
claude -w feat/api-tests &
# Method 2: Using /parallel-agents command
/parallel-agents
# Interactive prompt:
# How many agents? 3
# Agent 1 task: Implement auth module with JWT
# Agent 2 task: Build dashboard with charts
# Agent 3 task: Write API integration tests
Monitor Progress
# Check all worktrees
git worktree list
# Check agent status (if using Claude Peers)
/peers status
Merge Results
# After all agents complete:
git checkout main
git merge feat/auth
git merge feat/dashboard
git merge feat/api-tests
Use Cases
Feature Parallelism
Work on 3 independent features at once:
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 · 229 lines · 14 tokens per session scan A 840b91198bb2
ccc-parallel is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 1,385 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
my_send
Complete pre-commit workflow - runs review, docs, and commit in sequence.
my_commit
Create a well-formatted commit following project conventions (auto-detects Conventional Commits, Gitmoji, or Simple style).
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
commit
Run the full commit gate — the only sanctioned path to a git commit.