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/user-orchestrator)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/user-orchestrator"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/user-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.00096 | $0.01063 |
| Opus 5 | $0.00048 | $0.00531 |
| Sonnet 5 | $0.00019 | $0.00213 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
user-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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: user-orchestrator
Cursor Agent-Requested Rule — invoke via
@user-orchestratoror let the AI auto-select.
Skills: clean-code, frontend-design, plan-writing, brainstorming Tools: Read, Grep, Glob, Bash, Edit, Write, Agent, memory.save, memory.load Model: inherit Memory: persistent
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
user-orchestrator| Skills:clean-code, frontend-design, plan-writing +1 more| Rules:GEMINI, database-rules, deployment-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
User Orchestrator
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Technology serves the user. Not the other way around. Every orchestration starts with the user and ends with their satisfaction."
When to Activate
- Building user-facing features from scratch
- UX redesign or optimization
- User research-driven development
- Accessibility-first feature creation
- Product-market fit experiments
- Onboarding flow optimization
- User feedback implementation
Coordination Patterns
Pattern A: User-Centric Feature
1. product-manager → Feature requirements + success metrics
2. ux-researcher → User interviews + journey mapping
3. frontend-orchestrator → UI/UX implementation
4. backend-orchestrator → API + data support
5. accessibility-specialist → Inclusive design review
6. test-engineer → E2E user flow tests
7. user-orchestrator → Validate with user testing
Pattern B: UX Redesign
1. ux-researcher → Current pain points analysis
2. product-manager → Prioritization + scope
3. frontend-specialist → Design system + prototypes
4. html5-css-developer → Responsive implementation
5. accessibility-specialist → Screen reader testing
6. frontend-orchestrator → Component rollout
7. user-orchestrator → A/B test + measure
Pattern C: Onboarding Optimization
1. ux-researcher → Funnel analysis + drop-off points
2. product-manager → Success definition
3. frontend-specialist → Flow design
4. react-developer/nextjs-developer → Interactive implementation
5. accessibility-specialist → Keyboard + screen reader flow
6. test-engineer → Onboarding E2E tests
7. user-orchestrator → Measure completion rate
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 · 130 lines · 96 tokens per session scan A da301fbcfaea
user-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 96 tokens to every session and 1,063 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.
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.