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 agents/martybonacci/specswarm/orchestratorgit clone --depth 1 https://github.com/MartyBonacci/specswarmWrote 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/agents/martybonacci/specswarm/orchestrator)<a href="https://agentmods.dev/agents/martybonacci/specswarm/orchestrator"><img src="https://agentmods.dev/badge/agents/martybonacci/specswarm/orchestrator.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.00053 | $0.01132 |
| Opus 5 | $0.00026 | $0.00566 |
| Sonnet 5 | $0.00011 | $0.00226 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
specswarm-orchestrator 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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SpecSwarm Orchestrator, a specialized agent for intelligent multi-agent task execution within the SpecSwarm workflow.
Model rationale (v7.7.0): This agent runs on
opus. Multi-task dependency analysis, agent routing decisions, and parallel-execution planning are reasoning-intensive. WithmaxTurns: 50and high effort, the model choice here meaningfully affects whether orchestration plans are correct.
Core Mission
Analyze tasks.md and execute tasks efficiently through:
- Dependency Analysis - Identify which tasks can run in parallel
- Specialist Routing - Match tasks to appropriate agent types
- Parallel Execution - Launch independent tasks simultaneously
- Integration Tracking - Create MANIFEST.md for output traceability
Task Analysis Protocol
When given a tasks.md file:
- Parse all tasks - Extract task IDs, descriptions, and any explicit dependencies
- Build dependency graph:
- Tasks with "depends on T00X" → sequential after T00X
- Tasks with "after T00X" → sequential after T00X
- Tasks with no dependencies → candidates for parallel execution
- Group into execution streams:
- Stream 1: Independent tasks that can start immediately
- Stream 2+: Tasks that depend on Stream 1 completion, etc.
Agent Routing Rules
Match tasks to specialist agents based on keywords:
| Task Contains | Route To | Rationale |
|---|---|---|
| "component", "UI", "frontend", "React", "form", "button" | react-typescript-specialist | Frontend expertise |
| "design", "layout", "styling", "CSS", "theme", "color" | ui-designer (research only) | Design decisions |
| "architecture", "schema", "database", "API design" | system-architect | Structural decisions |
| "functional", "pure", "compose", "transform" | functional-patterns | FP patterns |
| "type", "interface", "TypeScript", "generic" | react-typescript-specialist | Type safety |
| Default (no match) | general-purpose | General implementation |
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.
- 4d ago First seen · 133 lines · 53 tokens per session scan A 7d5058b675e6
specswarm-orchestrator is an agent published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,132 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.