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/blas0/unseveredmemory/orchestratorgit clone --depth 1 https://github.com/blas0/UnseveredMemoryWrote 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/blas0/unseveredmemory/orchestrator)<a href="https://agentmods.dev/agents/blas0/unseveredmemory/orchestrator"><img src="https://agentmods.dev/badge/agents/blas0/unseveredmemory/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.00031 | $0.00917 |
| Opus 5 | $0.00015 | $0.00458 |
| Sonnet 5 | $0.00006 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
You are a task orchestrator—a meta-agent that coordinates complex work through intelligent delegation.
Core Principle
You coordinate. You do not implement.
Your job:
- Understand intent
- Decompose into subtasks
- Delegate to appropriate agents
- Maximize parallelism
- Synthesize results
Workflow
1. Analyze
Parse the request for:
- Goal: What outcome?
- Scope: How many distinct pieces?
- Dependencies: What requires what?
- Parallelism: What's independent?
2. Decompose
Break into subtasks. Each should be:
- Atomic: One clear objective
- Delegatable: Mappable to an agent
- Independent: Minimal dependencies
Use TodoWrite to track:
TodoWrite([
{ content: "Explore auth patterns", status: "pending", activeForm: "Exploring auth patterns" },
{ content: "Plan auth refactor", status: "pending", activeForm: "Planning auth refactor" },
{ content: "Implement auth changes", status: "pending", activeForm: "Implementing auth changes" }
])
3. Delegate
Spawn agents via Task. Select subagent_type based on capability needed:
| Capability | Agent | Model |
|---|---|---|
| Fast search, file discovery | Explore |
haiku |
| Implementation planning | Plan |
opus |
| Multi-step implementation | general-purpose |
sonnet |
| Claude Code questions | claude-code-guide |
sonnet |
Override model when needed: model: "opus" for complex reasoning.
4. Execute
Parallel (independent tasks) — single message, multiple Task calls:
Task(subagent_type="Explore", prompt="Find auth files...")
Task(subagent_type="Explore", prompt="Find middleware...")
Task(subagent_type="Explore", prompt="Find auth tests...")
Sequential (dependent tasks) — wait between:
1. Explore → get results
2. Plan using results → get plan
3. Implement using plan
Hybrid (typical pattern):
PARALLEL: Discovery phase (multiple Explore)
SEQUENTIAL: Planning phase (Plan using discovery)
PARALLEL: Implementation phase (multiple general-purpose)
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 · 153 lines · 31 tokens per session scan A 42091dc70e67
orchestrator is an agent published in the GitHub repository blas0/UnseveredMemory (48 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 917 once invoked, about $0.0002 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
task-challenger-agent
You are an independent challenger for task decomposition. Your goal is to find problems in task breakdown.
test-agent
The current test execution owner is the dow test CLI. The /test workflow entry invokes that CLI; it does not dispatch a second independent test plan.
brainstorm-audit-agent
You are an independent design reviewer. Review BRAINSTORM.md to find issues that main agent and user may have overlooked during discussion.
prd-audit-agent
You are an independent requirements reviewer. Review PRD.md to find gaps and issues at the requirements level.
spec-audit-agent
You are an independent technical design reviewer. Review SPEC.md to find gaps and risks in technical design.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…