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 rules/madebyaris/cursor-composer-rules/composer-orchestrationgit clone --depth 1 https://github.com/madebyaris/cursor-composer-rulesWrote 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/cursor-composer-rules/composer-orchestration)<a href="https://agentmods.dev/rules/madebyaris/cursor-composer-rules/composer-orchestration"><img src="https://agentmods.dev/badge/rules/madebyaris/cursor-composer-rules/composer-orchestration.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.00020 | $0.01751 |
| Opus 5 | $0.00010 | $0.00875 |
| Sonnet 5 | $0.00004 | $0.00350 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
composer-orchestration 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composer orchestration
Use when work spans multiple files, parallel tracks, long-running commands, plan mode, or you need context isolation. For single-file edits, stay in the parent agent.
Companion rules: composer-core (intent, confusion weight, handoff), composer-reasoning (tradeoffs on complex work), composer-fullstack-delivery (vertical slice + continue handoff), composer-debugging (repro before fan-out), composer-verification (status labels).
When to delegate
Delegate for isolation or parallelism, not because tools exist.
| Situation | Delegate to |
|---|---|
| Wide codebase search with noisy intermediate output | built-in Explore subagent |
| Long or verbose shell output | built-in Bash subagent or background shell |
| Browser/UI verification (DOM noise, screenshots) | built-in Browser subagent |
| Independent parallel tracks (API + docs, client + server read-only survey) | multiple subagents in one batch |
| Skeptical re-check before marking done | custom verifier (.cursor/agents/verifier.md) |
| Isolated debug with full stack context | custom debugger (.cursor/agents/debugger.md) |
When not to delegate
- Single-file edit, one test run, one MCP call.
- One-shot tasks ("format imports", "generate changelog") — use a skill or do inline.
- Spawning many subagents for work one agent can finish in a few tool calls.
- Delegating because the model is tool-capable — prefer parent tools first.
Default: parent does the work unless isolation or parallelism clearly wins.
Subagent prompt contract
Subagents start with a clean context — they do not see prior chat history. Every delegation prompt must include:
- Goal — observable outcome.
- Constraints — what not to change, style, scope limits.
- Pointers — file paths, symbols, error messages, branch names.
- Definition of done — what "finished" means for this handoff.
- Return shape — summary format the parent needs (not raw logs).
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.
- 5d ago First seen · 140 lines · 20 tokens per session scan A 5cd4be4b65ef
composer-orchestration is a cursor rule published in the GitHub repository madebyaris/cursor-composer-rules (3 stars, last pushed 17d ago), licensed MIT. It adds 20 tokens to every session and 1,751 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.
Other cursor rules, from other repositories
cursorrules
You are an expert in WordPress, PHP, and Gutenberg block development.
golang
Follow effective Go conventions. Use table-driven tests. Handle all errors explicitly. No blank error returns. Use context.Context for cancellation and timeouts. Prefer composition over embedding.
module-01
Follow module 01 conventions. Keep boundaries clean. Use dependency injection. No circular imports. Document public APIs with JSDoc.
module-02
Follow module 02 conventions. Keep boundaries clean. Use dependency injection. No circular imports. Document public APIs with JSDoc.
module-03
Follow module 03 conventions. Keep boundaries clean. Use dependency injection. No circular imports. Document public APIs with JSDoc.
module-04
Follow module 04 conventions. Keep boundaries clean. Use dependency injection. No circular imports. Document public APIs with JSDoc.