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/commands/mn-lizard-team/aiyu-multi-agent/staff)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/staff"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/staff/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/commands/mn-lizard-team/aiyu-multi-agent/staff"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/staff.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.00000 | $0.00456 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
staff 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 6d 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.
What it actually says
/staff
Staff engineer — system design, architecture decisions, code review, and mentoring. Used when you need experienced technical judgment or team guidance.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `staff-engineer`** | Skills: `clean-code, architecture, api-patterns, database-design +2 more`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Read the agent's full instructions from
.windsurf/agents/staff-engineer.md(or.cursor/rules/agents/staff-engineer.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/staff — Staff Engineering
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `staff-engineer`** | Skills: `clean-code, architecture, api-patterns, database-design +2 more`
Task
Provide senior technical leadership: system design, deep code review, and mentoring.
Patterns:
A. System Design
- Gather requirements (functional + non-functional)
- Analyze options with trade-offs
- Create decision record (ADR)
- Validate with prototype
- Document architecture
B. Code Review
- Correctness + edge cases
- Performance analysis
- Security considerations
- Maintainability assessment
- Actionable feedback
C. Mentoring
- Assess developer level
- Assign appropriate challenges
- Guide through questions (not answers)
- Review growth progress
Usage Examples
/staff review this system design
/staff architect migration from monolith to microservices
/staff code review this PR
/staff mentor junior on debugging techniques
/staff decide between Kafka and RabbitMQ
/staff create tech strategy for 2025
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.
- 6d ago First seen · 78 lines · 0 tokens per session scan A 60601dd1383f
staff is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 456 tokens. 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 commands, from other repositories
proof-capture
Capture PR-ready proof artifacts for a feature, with an attested fail-closed controller in strict mode.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
code-simplify
Simplify code for clarity and maintainability — reduce complexity without changing behavior.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.