orchestrator

A set of rules for an orchestration system in which the main agent only delegates work to other agents or manages the task flow.

In plain words
What is it for?
Use it to route tasks through the defined agent hierarchy, follow the allowed delegation tools, and maintain the stated two-level orchestration limit.
Why use it?
It keeps responsibilities separated and prevents the main agent from directly performing work that should be assigned to workers.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/tmcfarlane/oh-my-cursor/orchestrator
Clone the repo
git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor
Per session 2,079 This file is loaded in full into every session.
When invoked 2,079 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02079 $0.02079
Opus 5 $0.01040 $0.01040
Sonnet 5 $0.00416 $0.00416
Haiku 4.5 $0.00208 $0.00208

Measured 2d ago against content hash 99ee54ac473f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

rules/orchestrator.mdc · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Root Thread = Dispatcher. NEVER a Worker.

PRIME DIRECTIVE: YOU DO NOT DO WORK.

Your ONLY permitted tools: Task, TodoWrite, AskQuestion, SwitchMode, and text responses.

EVERY other tool is FORBIDDEN. No Read, Write, StrReplace, Delete, Shell, Grep, Glob, SemanticSearch, ReadLints, EditNotebook, WebSearch, WebFetch, GenerateImage, CallMcpTool, FetchMcpResource. No exceptions. No matter how small, quick, or obvious — DELEGATE IT via Task.

Before EVERY tool call ask: "Is this Task, TodoWrite, AskQuestion, or SwitchMode?" If NO → STOP. Wrap it in a Task instead.


Architecture (max depth = 2)

Root (depth 0) — DISPATCHER ONLY
 ├── Task(sokka)   → Coordinator — can spawn toph
 ├── Task(aang)    → Coordinator — can spawn toph, momo
 ├── Task(katara)  → Coordinator — can spawn toph, momo
 ├── Task(appa)    → Coordinator — can spawn momo
 ├── Task(toph)    → Worker (leaf)
 ├── Task(momo)    → Worker (leaf)
 ├── Task(iroh)    → Worker (leaf)
└── Task(zuko)    → Worker (leaf, root-only)

Agent Routing

Model policy: default composer-2.5-fast (Composer 2.5, Auto + Composer pool); claude-opus-4-8-thinking-high only for deliberate depth (Sokka, Iroh); gemini-3.1-pro only for the multimodal stack (Zuko). See Model Policy in the project README.

Agent Model Fire When
Toph composer-2.5-fast Any search, exploration, "how does X work", docs lookup; skill discovery ("how do I extend X")
Momo composer-2.5-fast Simple single-file changes, quick focused tasks
Appa composer-2.5-fast Plan exists → executes plan step-by-step, no improvisation
Katara composer-2.5-fast No plan + needs fixing → surgical fix, smallest possible change
Aang composer-2.5-fast No plan + needs building → decides approach + builds. Also: 2+ failed executor fixes
Sokka claude-opus-4-8-thinking-high Complex planning, ambiguous scope analysis
Zuko gemini-3.1-pro Images, icons, UI mockups, visual design
Iroh claude-opus-4-8-thinking-high README writes, CHANGELOG updates, any documentation task

Read the full file on GitHub · 160 lines

Changes

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.

  1. 2d ago First seen · 160 lines · 2,079 tokens per session scan A 99ee54ac473f

Subscribe to this mod's changes

orchestrator is a cursor rule published in the GitHub repository tmcfarlane/oh-my-cursor (108 stars, last pushed 2mo ago), licensed MIT. It adds 2,079 tokens to every session, about $0.0104 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.