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/protocol)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/protocol"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/protocol/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/protocol"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/protocol.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.00639 |
| Opus 5 | $0.00000 | $0.00319 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
protocol 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/protocol
API protocol selection, communication design, and MCP server building. Used when choosing between REST, GraphQL, gRPC, tRPC, WebSocket, SSE, or building MCP integrations.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `protocol-architect`** | 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 Behavior
- Follow the task steps defined below
- Apply the Socratic Gate: ask clarifying questions if requirements are unclear
- Report completion status at the end
/protocol — Protocol & Communication Design
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `protocol-architect`** | Skills: `clean-code, api-patterns, mcp-builder, architecture +1 more`
Task
Select the right protocol, design the API contract, and build communication architecture — including MCP servers for AI tool integration.
Steps:
-
Requirements Analysis
- Who consumes this API? (public, internal, frontend, AI)
- What patterns? (CRUD, real-time, streaming, event-driven)
- What constraints? (latency, bandwidth, type safety)
-
Protocol Selection
- REST → public CRUD APIs
- GraphQL → complex queries, multi-entity
- gRPC → microservices, high throughput
- tRPC → TypeScript full-stack
- WebSocket → bidirectional real-time
- SSE → server push, simple
- Message Queue → async, decoupled
-
Contract Design
- Define schema (OpenAPI / GraphQL SDL / Protobuf / Zod)
- Design error format
- Plan auth strategy
- Set versioning policy
-
MCP Server (if AI integration)
- Define tools with JSON Schema
- Implement handlers
- Add resources for static data
- Configure transport (stdio / SSE)
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 · 98 lines · 0 tokens per session scan A 0a583076cb11
protocol 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 639 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
brainstorm
Command dispatcher for brainstorm.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
sparc-integration
🔗 System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
trex.kind.new
Generate a complete CRUD entity (Kind) using the automated generator script.
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.