orchestrator-sub

orchestrator-sub is a cursor rule for Cursor from FASFG5T5/agent-orchestration. It costs 11 tokens per session (502 once invoked), scanned A, original, MIT.

Rules for smaller coding agents that work on individual tasks under the direction of a main agent. They cover claiming work, checking shared context, locking files, reporting progress, and finishing the task.

In plain words
What is it for?
Use them to coordinate delegated coding tasks, record findings and decisions, protect files during edits, and report task completion.
Why use it?
They reduce duplicated work and conflicting edits when several agents or sessions work in the same project.

Cursor rule for Cursor

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/fasfg5t5/agent-orchestration/orchestrator-sub
Clone the repo
git clone --depth 1 https://github.com/FASFG5T5/agent-orchestration

Made for: Cursor.

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

agentmods badge for orchestrator-sub

README.md
[![agentmods](https://agentmods.dev/badge/rules/fasfg5t5/agent-orchestration/orchestrator-sub.svg)](https://agentmods.dev/rules/fasfg5t5/agent-orchestration/orchestrator-sub)
Your own site
<a href="https://agentmods.dev/rules/fasfg5t5/agent-orchestration/orchestrator-sub"><img src="https://agentmods.dev/badge/rules/fasfg5t5/agent-orchestration/orchestrator-sub.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 502 The whole file, excluding the scripts and references it only reads on demand.
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.00011 $0.00502
Opus 5 $0.00005 $0.00251
Sonnet 5 $0.00002 $0.00100
Haiku 4.5 $0.00001 $0.00050

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

Security

Grade A, and why

orchestrator-sub 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 5d 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.

.cursor/rules/orchestrator-sub.mdc · 115 lines

What it actually says

Sub-Agent Rules

You are a sub-agent spawned to work on a specific task. Follow these rules.


⚠️ CRITICAL FIRST STEP ⚠️

You were spawned to work on a specific task. IMMEDIATELY claim it:

claim_todo:
  title: "<the task you were given>"
  description: "<details if any>"

DO NOT start coding until you have claimed your task.

This:

  1. Registers you with the orchestrator
  2. Creates the task if it doesn't exist
  3. Claims it so no other agent works on it
  4. Returns your agent ID and task ID

After Claiming

  1. Check context to understand the project:

    memory_get:
      key: "current_focus"
      namespace: "context"
    
  2. Check decisions to avoid contradicting them:

    memory_list:
      namespace: "decisions"
    
  3. Lock files before editing:

    lock_acquire:
      resource: "<file_path>"
      reason: "<what you're doing>"
    

While Working

Update progress periodically:

task_update:
  task_id: "<your_task_id>"
  progress: 50

Store important findings:

memory_set:
  key: "<finding>"
  value: "<details>"
  namespace: "findings"

When Done

  1. Complete the task:

    task_complete:
      task_id: "<your_task_id>"
      output: "<summary of what you did>"
    
  2. Release any locks:

    lock_release:
      resource: "<file_path>"
    
  3. Unregister:

    agent_unregister
    

If Blocked

Store the blocker so others know:

memory_set:
  key: "blocker_<issue>"
  value: "<what's blocking you>"
  namespace: "blockers"

Important Rules

  1. ALWAYS claim your task first with claim_todo
  2. ALWAYS lock files before editing shared resources
  3. ALWAYS complete your task when done
  4. Check shared memory before making decisions that affect others
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. 5d ago First seen · 115 lines · 11 tokens per session scan A 447d2289e6ff

Subscribe to this mod's changes

orchestrator-sub is a cursor rule published in the GitHub repository FASFG5T5/agent-orchestration (1 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 502 once invoked, about $0.0001 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-31.