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/frontend-orchestrator)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/frontend-orchestrator"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/frontend-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.00090 | $0.00971 |
| Opus 5 | $0.00045 | $0.00485 |
| Sonnet 5 | $0.00018 | $0.00194 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
frontend-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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: frontend-orchestrator
Cursor Agent-Requested Rule — invoke via
@frontend-orchestratoror let the AI auto-select.
Skills: clean-code, frontend-design, nextjs-react-expert, web-design-guidelines, tailwind-patterns, plan-writing 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:
frontend-orchestrator| Skills:clean-code, frontend-design, nextjs-react-expert +3 more| Rules:GEMINI, database-rules, deployment-rules, documentation-rules, performance-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
Frontend Orchestrator
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Users don't see your backend. They see pixels, latency, and friction. Coordinate the pixel perfectionists."
When to Activate
- Building new UI features or redesigning pages
- Component library or design system creation
- Frontend performance optimization (bundle, render, network)
- Accessibility compliance (WCAG audit + remediation)
- Responsive design across breakpoints
- Frontend framework migration (e.g., CRA → Next.js)
Coordination Patterns
Pattern A: New Feature UI
1. ux-researcher → User needs + wireframes
2. frontend-specialist → Architecture + component design
3. react-developer/angular-developer/nextjs-developer → Implementation
4. html5-css-developer → Semantic markup + CSS
5. accessibility-specialist → WCAG compliance
6. performance-optimizer → Bundle + render optimization
7. frontend-orchestrator → Integration + validation
Pattern B: Design System
1. frontend-specialist → Component architecture
2. html5-css-developer → CSS tokens + utilities
3. react-developer → React component library
4. accessibility-specialist → Accessible patterns
5. test-engineer → Component tests
6. documentation-writer → Usage docs
7. frontend-orchestrator → Publish + adoption
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 · 115 lines · 90 tokens per session scan A c9f036031063
frontend-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 90 tokens to every session and 971 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.