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.
npx agentmods add commands/mn-lizard-team/aiyu-multi-agent/protocol-orchestrationgit 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/protocol-orchestration)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/protocol-orchestration"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/protocol-orchestration.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.00000 | $0.00871 |
| Opus 5 | $0.00000 | $0.00436 |
| Sonnet 5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
protocol-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 5d 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.
/protocol-orchestration
Multi-agent protocol coordination for end-to-end API lifecycle. Orchestrates protocol-architect, backend, frontend, security, and devops for API design, migration, governance, and MCP ecosystem building.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `protocol-orchestrator`** | Skills: `clean-code, api-patterns, mcp-builder, architecture +1 more`
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.
/protocol-orchestration — API Lifecycle 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: `protocol-orchestrator`** | Skills: `clean-code, api-patterns, mcp-builder, architecture +1 more`
Task
Coordinate multiple agents for full API lifecycle — from protocol selection to deployment and governance.
Patterns:
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.
- 5d ago First seen · 115 lines · 0 tokens per session scan A a595e12c3df1
protocol-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 871 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-08-31.
Other commands, from other repositories
dashboard-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
dashboard-session-abort-all
Abort multiple running sessions (asks which). Usage /dashboard:session-abort-all.
dashboard-session-rename
Rename a session. Usage /dashboard:session-rename.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
rn-feature-dev
Guided feature development for React Native — explore codebase, design architecture, implement, verify live on device, and review quality.