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-specialist)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/frontend-specialist"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/frontend-specialist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/frontend-specialist"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/frontend-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00077 | $0.02589 |
| Opus 5.5 | $0.00031 | $0.01036 |
| Sonnet 5.5 | $0.00015 | $0.00518 |
| Haiku 4.5 | $0.00008 | $0.00259 |
Grade A, and why
frontend-specialist 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 2mo 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: frontend-specialist
Cursor Agent-Requested Rule — invoke via
@frontend-specialistor let the AI auto-select.
Skills: clean-code, nextjs-react-expert, web-design-guidelines, tailwind-patterns, frontend-design, frontend-design-process, lint-and-validate Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
frontend-specialist| Skills:clean-code, nextjs-react-expert, web-design-guidelines +3 more| Rules:GEMINI, code-quality-rules, database-rules, documentation-rules, performance-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- React/Next.js components
- UI styling
- state management
- responsive design
- frontend architecture
Senior Frontend Architect
You are a Senior Frontend Architect who designs and builds frontend systems with long-term maintainability, performance, and accessibility in mind.
📑 Quick Navigation
Design Process
- Your Philosophy
- Deep Design Thinking (Mandatory)
- Design Commitment Process
- Modern SaaS Safe Harbor (Forbidden)
- Layout Diversification Mandate
- Purple Ban & UI Library Rules
- The Maestro Auditor
- Reality Check (Anti-Self-Deception)
Technical Implementation
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.
- 2mo ago First seen · 289 lines · 77 tokens per session scan A eb3c03597466
frontend-specialist is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (8 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 2,589 once invoked, about $0.0003 per session on Opus 5.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.
frontend-specialist compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| frontend-specialistMN-Lizard-Team/aiyu-multi-agent | Cursor rule | 8 | 5mo ago | Apache-2.0 | A | 77 | Cursor |
| nextjs-react-tailwind-cursorrules-prompt-filePatrickJS/awesome-cursorrules | Cursor rule | 41k | 5mo ago | CC0-1.0 | A | 891 | Cursor |
| chakra-ui-best-practicesholtwood/awesome-cursorrules-zh | Cursor rule | 241 | 18d ago | MIT | A | 0 | Cursor |
| react-components-creation-cursorrules-prompt-filePatrickJS/awesome-cursorrules | Cursor rule | 41k | 5mo ago | CC0-1.0 | A | 355 | Cursor |
| ui-patternsproSamik/starterkit-nextjs-aisdk-betterauth-polar | Cursor rule | 4 | 1y ago | MIT | A | 0 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 185k | 8d ago | MIT | A | 604 | Cursor |
| angular-20angular/angular | Cursor rule | 101k | yesterday | MIT | A | 0 | Cursor |