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/tpavanipradeep/everything-claude-code/orchestrategit clone --depth 1 https://github.com/tpavanipradeep/everything-claude-codeWhat 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.00008 | $0.00600 |
| Opus 5 | $0.00004 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
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 2d 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.
This is a copy
100% identical to orchestrate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Command
Orchestrate multiple specialized agents for this complex task: $ARGUMENTS
Your Task
- Analyze task complexity and break into subtasks
- Identify optimal agents for each subtask
- Create execution plan with dependencies
- Coordinate execution - parallel where possible
- Synthesize results into unified output
Available Agents
| Agent | Specialty | Use For |
|---|---|---|
| planner | Implementation planning | Complex feature design |
| architect | System design | Architectural decisions |
| code-reviewer | Code quality | Review changes |
| security-reviewer | Security analysis | Vulnerability detection |
| tdd-guide | Test-driven dev | Feature implementation |
| build-error-resolver | Build fixes | TypeScript/build errors |
| e2e-runner | E2E testing | User flow testing |
| doc-updater | Documentation | Updating docs |
| refactor-cleaner | Code cleanup | Dead code removal |
| go-reviewer | Go code | Go-specific review |
| go-build-resolver | Go builds | Go build errors |
| database-reviewer | Database | Query optimization |
Orchestration Patterns
Sequential Execution
planner → tdd-guide → code-reviewer → security-reviewer
Use when: Later tasks depend on earlier results
Parallel Execution
┌→ security-reviewer
planner →├→ code-reviewer
└→ architect
Use when: Tasks are independent
Fan-Out/Fan-In
┌→ agent-1 ─┐
planner →├→ agent-2 ─┼→ synthesizer
└→ agent-3 ─┘
Use when: Multiple perspectives needed
Execution Plan Format
Phase 1: [Name]
- Agent: [agent-name]
- Task: [specific task]
- Depends on: [none or previous phase]
Phase 2: [Name] (parallel)
- Agent A: [agent-name]
- Task: [specific task]
- Agent B: [agent-name]
- Task: [specific task]
- Depends on: Phase 1
Phase 3: Synthesis
- Combine results from Phase 2
- Generate unified output
Coordination Rules
- Plan before execute - Create full execution plan first
- Minimize handoffs - Reduce context switching
- Parallelize when possible - Independent tasks in parallel
- Clear boundaries - Each agent has specific scope
- Single source of truth - One agent owns each artifact
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.
- 2d ago First seen · 89 lines · 8 tokens per session scan A 9784d1491f05
orchestrate is a command published in the GitHub repository tpavanipradeep/everything-claude-code (103 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 600 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orchestrate, differing in 0 lines, and is treated as a copy.
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.