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/fmarzochi/egc/orchestrategit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/orchestrate)<a href="https://agentmods.dev/commands/fmarzochi/egc/orchestrate"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/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.00008 | $0.00603 |
| Opus 5 | $0.00004 | $0.00302 |
| Sonnet 5 | $0.00002 | $0.00121 |
| 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 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 — 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.
- today First seen · 89 lines · 8 tokens per session scan A bc5e7b1cef02
orchestrate is a command published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 603 once invoked, about $0.0000 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
demand-discovery
Run automated niche demand discovery research across 7 data sources and 26 categories.
tdd-workflow
Implement the behavior described in $ARGUMENTS using strict TDD. Follow this exact sequence. Do not collapse phases. Each gate requires actual test runner output.
api-add-endpoint
Create a new API endpoint. $ARGUMENTS should describe the endpoint (e.g., "POST /api/users - create a user").
code-review
Review the code changes in this project. For each file changed.
refactor-file
Refactor the file specified in $ARGUMENTS following project conventions.
api-test-endpoint
Test the API endpoint specified in $ARGUMENTS.