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/thelobbi/claude/cc-orchestrategit clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/thelobbi/claude/cc-orchestrate)<a href="https://agentmods.dev/commands/thelobbi/claude/cc-orchestrate"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/cc-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.1 | $0.00000 | $0.03961 |
| Opus 5 | $0.00000 | $0.01980 |
| Sonnet 5 | $0.00000 | $0.00792 |
| Haiku 4.5 | $0.00000 | $0.00396 |
Grade A, and why
cc-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 5d 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 — 610 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cc-orchestrate — Agent Team Templates & Multi-Agent Orchestration
Deploy pre-built agent team configurations for common development patterns. Choose between subagent patterns (hub-and-spoke) and full Agent Teams (mesh coordination) based on your task complexity.
Usage
/cc-orchestrate # Interactive template picker
/cc-orchestrate --template builder-validator # Deploy specific template
/cc-orchestrate --template qa-swarm # QA testing swarm
/cc-orchestrate --list # List all available templates
/cc-orchestrate --status # Check running teams/subagents
/cc-orchestrate --dry-run # Show template without deploying
/cc-orchestrate --worktree # Set up git worktrees for parallel agents
When to Use Subagents vs Agent Teams
Decision Framework
Does the task need workers to communicate with each other?
├── NO → Use Subagents (hub-and-spoke)
│ • Workers report results to parent only
│ • Lower token cost (results summarized)
│ • No setup needed (built-in)
│ • Best for: research, review, focused deep-dives
│
└── YES → Use Agent Teams (mesh network)
• Workers message each other directly
• Shared task list with self-claiming
• Higher cost (~3-5x, each is a full session)
• Best for: multi-component features, debates, cross-layer work
Cost Comparison
| Pattern | Agents | Tokens/Task | Best For |
|---|---|---|---|
| Single agent | 1 | ~50k | Simple changes |
| Subagents | 1 lead + 2-4 workers | ~100-200k | Focused parallel work |
| Agent Team (small) | 3-5 teammates | ~250-500k | Multi-component features |
| Agent Team (swarm) | 5-10 teammates | ~500k-1M | Large-scale review/QA |
Template Library
Template 1: Builder-Validator (Subagent Pattern)
When: Any implementation task where quality matters. Pattern: Builder implements, Validator reviews and catches issues.
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.
- 5d ago First seen · 610 lines · 0 tokens per session scan A 7eff22733934
cc-orchestrate is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,961 tokens. 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.