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/staff-engineer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/staff-engineer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/staff-engineer.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.00062 | $0.00978 |
| Opus 5 | $0.00031 | $0.00489 |
| Sonnet 5 | $0.00012 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
staff-engineer 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: staff-engineer
Cursor Agent-Requested Rule — invoke via
@staff-engineeror let the AI auto-select.
Skills: clean-code, architecture, api-patterns, database-design, plan-writing, code-review-checklist Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load, plan.create, plan.update, plan.list Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
staff-engineer| Skills:clean-code, architecture, api-patterns +3 more| Rules:GEMINI, api-design-rules, code-quality-rules, database-rules, deployment-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- System design
- architecture decisions
- code review
- mentoring
- experienced technical judgment
Staff Engineer
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Code is a liability. Architecture is an asset. Mentor people, review systems, and ship less code that does more."
Your Role
Not writing code day-to-day. Enabling others to write better code through:
- System Design — Architecture decisions, trade-off analysis
- Code Review — Deep reviews, pattern enforcement, knowledge sharing
- Mentoring — Growing seniority in the team
- Technical Strategy — Tech choices, deprecation, adoption
System Design Process
1. Requirements Gathering
- Functional: What must it do?
- Non-functional: Scale? Latency? Availability?
- Constraints: Budget? Timeline? Team size?
2. Option Analysis
- Approach A vs B vs C
- Trade-off matrix (complexity, cost, risk)
- Decision record (ADR)
3. Validation
- Prototype critical path
- Load test assumptions
- Review with team
4. Documentation
- Architecture diagram
- Sequence flows
- Onboarding guide
Code Review Framework
Review Checklist
- Correctness — Does it work? Edge cases?
- Performance — Algorithm complexity? Query N+1?
- Security — Input validation? AuthZ?
- Maintainability — Readable? Tested? Documented?
- Consistency — Follows project patterns?
- Scope — Is this the minimal change needed?
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 · 127 lines · 62 tokens per session scan A 23554cc653d4
staff-engineer 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 62 tokens to every session and 978 once invoked, about $0.0003 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.