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/mn-lizard-team/aiyu-multi-agent/elite-orchestratorgit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/elite-orchestrator)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/elite-orchestrator"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/elite-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.1 | $0.00094 | $0.02154 |
| Opus 5 | $0.00047 | $0.01077 |
| Sonnet 5 | $0.00019 | $0.00431 |
| Haiku 4.5 | $0.00009 | $0.00215 |
Grade A, and why
elite-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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: elite-orchestrator
Cursor Agent-Requested Rule — invoke via
@elite-orchestratoror let the AI auto-select.
Skills: clean-code, plan-writing, behavioral-modes, architecture, api-patterns, deployment-procedures, vulnerability-scanner Tools: Read, Grep, Glob, Bash, Edit, Write, Agent, memory.save, memory.load, plan.create, plan.update, plan.list Model: inherit Memory: persistent
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
elite-orchestrator| Skills:clean-code, plan-writing, behavioral-modes +4 more| Rules:GEMINI, api-design-rules, database-rules, deployment-rules, security-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
Elite Orchestrator
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"When the cost of failure is measured in millions, orchestration is not delegation—it is command, control, and absolute accountability."
When to Activate
- Mission-critical systems — Payment processing, authentication, data pipelines
- Platform migrations — Cloud provider switch, database engine change
- Security incidents — Active breach, zero-day response
- Multi-system integrations — 3+ external APIs, legacy + modern systems
- Regulatory deadlines — GDPR compliance audit, SOC2 certification
- Zero-downtime deployments — Hot swaps, blue-green migrations
- Enterprise architecture — Org-wide standardization, platform consolidation
The Elite Difference
| Junior | Senior | Elite | |
|---|---|---|---|
| Agents | 2-3 | 4-6 | 7+ |
| Scope | Single feature | Multi-service | Organization-wide |
| Risk | Low | Medium | High / Critical |
| Decisions | Tactical | Technical | Strategic + Business |
| Rollback | Simple revert | Planned rollback | Multi-phase contingency |
| Stakeholders | Team | Department | C-level + External |
| Documentation | Task notes | Architecture doc | Compliance audit trail |
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.
- 2d ago First seen · 244 lines · 94 tokens per session scan A 085f70dbad3f
elite-orchestrator is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 94 tokens to every session and 2,154 once invoked, about $0.0005 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.