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/user-orchestration)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/user-orchestration"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/user-orchestration/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/user-orchestration"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/user-orchestration.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.00761 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
user-orchestration 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/user-orchestration
User experience orchestration — coordinates product, UX research, frontend, backend, and accessibility for user-centric feature development.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `user-orchestrator`** | Skills: `clean-code, frontend-design, plan-writing, brainstorming`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Response Structure
After the activation line, always structure your response with these sections in order:
- Mission Brief — objective + scope + constraints
- Execution Plan — tasks with status (pending/in_progress/completed)
- Agent Delegation Matrix — which agents handle what
- Risk Register — top risks with likelihood/impact/mitigation
- Quality Gates — criteria that must pass before proceeding
- Next Immediate Actions — concrete first steps
Keep output concise, operational, and accountable.
/user-orchestration — User-Centric Feature Coordination
$ARGUMENTS
Available Orchestration Tools
| Tool | Purpose |
|---|---|
agent.delegate |
Delegate sub-tasks to specialized agents (max depth 3) |
plan.create |
Create structured execution plan |
plan.update |
Update task status (pending → in_progress → completed) |
plan.list |
View plan progress |
memory.save |
Save context for cross-agent handoff |
memory.load |
Load saved context from previous agent |
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `user-orchestrator`** | Skills: `clean-code, frontend-design, plan-writing, brainstorming`
Task
Coordinate all disciplines around the user: research, design, implementation, and validation.
Patterns:
A. User-Centric Feature
- product-manager → Requirements + metrics
- ux-researcher → User research
- frontend-orchestrator → UI implementation
- backend-orchestrator → API + data
- accessibility-specialist → Inclusive design
- test-engineer → E2E user tests
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 · 105 lines · 0 tokens per session scan A c26007192b5e
user-orchestration 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 761 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
design
Command dispatcher for design.
brainstorm
Command dispatcher for brainstorm.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.