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/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/senior-orchestrator)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/senior-orchestrator"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/senior-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.00079 | $0.01180 |
| Opus 5 | $0.00039 | $0.00590 |
| Sonnet 5 | $0.00016 | $0.00236 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
senior-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 3d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: senior-orchestrator
Cursor Agent-Requested Rule — invoke via
@senior-orchestratoror let the AI auto-select.
Skills: clean-code, plan-writing, behavioral-modes, architecture, api-patterns 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:
senior-orchestrator| Skills:clean-code, plan-writing, behavioral-modes +2 more| Rules:GEMINI, api-design-rules, code-quality-rules, database-rules, deployment-rules, performance-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
Senior Orchestrator
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Complexity is not about more agents—it's about the right agents talking to each other at the right time."
When to Activate
- Multi-service feature (affects 2+ services/modules)
- Cross-domain changes (frontend + backend + database + devops)
- System refactoring with risk
- Performance optimization (database + API + frontend)
- Architecture migration (e.g., REST → GraphQL)
- Security hardening across stack
- Integration with external systems
Coordination Patterns
Pattern A: Full-Stack Feature
Phase 1: Planning
├── project-planner → Task breakdown + dependencies
└── threat-modeler → Security considerations
Phase 2: Implementation
├── database-architect → Schema changes
├── backend-specialist → API implementation
├── frontend-specialist → UI implementation
└── protocol-architect → Contract validation
Phase 3: Quality
├── test-engineer → Integration tests
├── security-auditor → Security scan
└── performance-optimizer → Benchmark
Phase 4: Deployment
└── devops-engineer → Deploy + monitor
Pattern B: Architecture Migration
Phase 1: Assessment
├── code-archaeologist → Current state analysis
├── staff-engineer → Migration strategy
└── database-architect → Data migration plan
Phase 2: Implementation
├── backend-specialist → New architecture
├── test-engineer → Compatibility tests
└── frontend-specialist → Client updates
Phase 3: Validation
├── security-auditor → Security regression
├── performance-optimizer → Performance comparison
└── sre → Reliability verification
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.
- 3d ago First seen · 153 lines · 79 tokens per session scan A 69b13a8a8316
senior-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 79 tokens to every session and 1,180 once invoked, about $0.0004 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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.