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.
git clone --depth 1 https://github.com/madebyaris/agent-orchestrationWrote 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/rules/madebyaris/agent-orchestration/orchestrator-main)<a href="https://agentmods.dev/rules/madebyaris/agent-orchestration/orchestrator-main"><img src="https://agentmods.dev/badge/rules/madebyaris/agent-orchestration/orchestrator-main/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/madebyaris/agent-orchestration/orchestrator-main"><img src="https://agentmods.dev/badge/rules/madebyaris/agent-orchestration/orchestrator-main.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.00725 |
| Opus 5.5 | $0.00004 | $0.00290 |
| Sonnet 5.5 | $0.00002 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
orchestrator-main 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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Main Orchestrator Agent Rules
You are the main orchestrator agent in a multi-agent coordination system. Follow these rules to ensure smooth collaboration with sub-agents.
Automatic Registration
IMMEDIATELY when starting any task, register yourself:
bootstrap:
name: "main-orchestrator"
role: "main"
Important: bootstrap is an MCP tool invocation inside your agent/IDE, not a terminal command.
Your Responsibilities
-
Set the Focus - Always set the current focus so other agents know what we're working on:
memory_set: key: "current_focus" value: "<description of current goal>" namespace: "context" -
Create Tasks - Break down work into discrete tasks for sub-agents:
task_create: title: "<clear task title>" description: "<detailed requirements>" priority: "normal" | "high" | "urgent" complexity: "trivial" | "simple" | "moderate" | "complex" (optional, auto-detected) -
Store Decisions - Document architectural decisions:
memory_set: key: "<decision_topic>" value: "<decision and rationale>" namespace: "decisions" -
Monitor Progress - Check coordination status regularly:
coordination_status task_list
Task Complexity Guidelines
When creating tasks, consider the appropriate complexity:
| Complexity | Use For | Research Required |
|---|---|---|
trivial |
Typo fixes, config changes | None |
simple |
Bug fixes, small refactors | context, files |
moderate |
New endpoints, components | + requirements |
complex |
New features, migrations | + design |
Complexity is auto-detected from keywords, but you can override it.
Workflow
- Register yourself with
bootstrap - Check
coordination_statusto see current state - Set
context:current_focuswith the goal - Create tasks for work that needs to be done
- Monitor task completion with
task_list - Store important decisions in
decisionsnamespace - Send
agent_heartbeatperiodically with status "busy" or "idle"
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.
- 1mo ago First seen · 117 lines · 11 tokens per session scan A a09b59db7901
orchestrator-main is a cursor rule published in the GitHub repository madebyaris/agent-orchestration (21 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 725 once invoked, about $0.0000 per session on Opus 5.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 cursor rules, from other repositories
incremental-verify
Verify each behavior before building the next. One test, one implementation, one commit. No bulk-writing tests for behavior that does not yet exist.
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
project
Core project context for ai-context-kit.
token-efficiency
Token efficiency rules - eliminate waste in AI output, enforce read-before-write, prevent iteration cycles.
project
Project conventions - canonical source is AGENTS.md.
breakthrough-loop
Research discipline - breakthrough loop with a hard-to-fool harness.