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-orchestrategit 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-orchestrate)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-orchestrate"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-orchestrate.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.01231 |
| Opus 5 | $0.00007 | $0.00616 |
| Sonnet 5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00001 | $0.00123 |
Grade A, and why
ccc-orchestrate 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Command
Sequential agent workflow for complex tasks.
Usage
/orchestrate [workflow-type] [task-description]
Workflow Types
feature
Full feature implementation workflow:
planner -> tdd-guide -> code-reviewer -> security-reviewer
bugfix
Bug investigation and fix workflow:
planner -> tdd-guide -> code-reviewer
refactor
Safe refactoring workflow:
architect -> code-reviewer -> tdd-guide
security
Security-focused review:
security-reviewer -> code-reviewer -> architect
Execution Pattern
For each agent in the workflow:
- Invoke agent with context from previous agent
- Collect output as structured handoff document
- Pass to next agent in chain
- Aggregate results into final report
Handoff Document Format
Between agents, create handoff document:
## HANDOFF: [previous-agent] -> [next-agent]
### Context
[Summary of what was done]
### Findings
[Key discoveries or decisions]
### Files Modified
[List of files touched]
### Open Questions
[Unresolved items for next agent]
### Recommendations
[Suggested next steps]
Example: Feature Workflow
/orchestrate feature "Add user authentication"
Executes:
-
Planner Agent
- Analyzes requirements
- Creates implementation plan
- Identifies dependencies
- Output:
HANDOFF: planner -> tdd-guide
-
TDD Guide Agent
- Reads planner handoff
- Writes tests first
- Implements to pass tests
- Output:
HANDOFF: tdd-guide -> code-reviewer
-
Code Reviewer Agent
- Reviews implementation
- Checks for issues
- Suggests improvements
- Output:
HANDOFF: code-reviewer -> security-reviewer
-
Security Reviewer Agent
- Security audit
- Vulnerability check
- Final approval
- Output: Final Report
Final Report Format
ORCHESTRATION REPORT
====================
Workflow: feature
Task: Add user authentication
Agents: planner -> tdd-guide -> code-reviewer -> security-reviewer
SUMMARY
-------
[One paragraph summary]
AGENT OUTPUTS
-------------
Planner: [summary]
TDD Guide: [summary]
Code Reviewer: [summary]
Security Reviewer: [summary]
FILES CHANGED
-------------
[List all files modified]
TEST RESULTS
------------
[Test pass/fail summary]
SECURITY STATUS
---------------
[Security findings]
RECOMMENDATION
--------------
[SHIP / NEEDS WORK / BLOCKED]
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 · 232 lines · 14 tokens per session scan A de6e70db0fe9
ccc-orchestrate 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,231 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).
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
adv-codex
Send a prompt to Codex CLI and return the response.
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]".