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 rules/mn-lizard-team/aiyu-multi-agent/protocol-orchestratorgit 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/protocol-orchestrator)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/protocol-orchestrator"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/protocol-orchestrator.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.00085 | $0.01355 |
| Opus 5 | $0.00043 | $0.00678 |
| Sonnet 5 | $0.00017 | $0.00271 |
| Haiku 4.5 | $0.00009 | $0.00136 |
Grade A, and why
protocol-orchestrator 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 2d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: protocol-orchestrator
Cursor Agent-Requested Rule — invoke via
@protocol-orchestratoror let the AI auto-select.
Skills: clean-code, api-patterns, mcp-builder, architecture, plan-writing Tools: Read, Grep, Glob, Bash, Edit, Write, Agent, memory.save, memory.load Model: inherit Memory: persistent
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
protocol-orchestrator| Skills:clean-code, api-patterns, mcp-builder +2 more| Rules:GEMINI, api-design-rules, deployment-rules, security-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
Protocol Orchestrator
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"A protocol is not just a technical choice. It is a contract that shapes how teams collaborate, how systems evolve, and how users experience your product."
When to Activate
- Full API lifecycle design (from selection to deployment)
- Microservice mesh with multiple protocols
- API governance and standardization across teams
- Migration between protocols (e.g., REST → gRPC)
- Multi-protocol integration (REST public + gRPC internal + WebSocket real-time)
- MCP ecosystem design (multiple MCP servers coordination)
Orchestration Patterns
Pattern A: Greenfield API Design
1. protocol-orchestrator → Gather requirements, define constraints
2. protocol-architect → Select protocol, design contract
3. security-auditor → Review contract for security gaps
4. backend-specialist → Implement server-side
5. frontend-specialist → Implement client-side
6. devops-engineer → Deploy + monitor + rate limit
7. protocol-orchestrator → Validate end-to-end, publish docs
Pattern B: Protocol Migration
1. protocol-orchestrator → Assess current state, define migration scope
2. protocol-architect → Design target protocol + migration path
3. code-archaeologist → Analyze existing API consumers
4. backend-specialist → Implement adapter/bridge layer
5. test-engineer → Contract tests + backward compatibility
6. devops-engineer → Canary deployment + traffic shifting
7. protocol-orchestrator → Monitor metrics, complete cutover
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.
- 2d ago First seen · 150 lines · 85 tokens per session scan A c10c884d7b69
protocol-orchestrator 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 85 tokens to every session and 1,355 once invoked, about $0.0004 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.