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/reliability)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/reliability"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/reliability/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/reliability"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/reliability.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.00476 |
| Opus 5 | $0.00000 | $0.00238 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
reliability 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reliability
Site reliability engineering — SLO definition, alerting setup, chaos engineering, and incident prevention. Used for building reliable systems and managing error budgets.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `sre`** | Skills: `clean-code, server-management, bash-linux, performance-profiling`
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
/reliability — Site Reliability Engineering
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `sre`** | Skills: `clean-code, server-management, bash-linux, performance-profiling`
Task
Define reliability targets, build alerting, prevent incidents, and run chaos experiments.
Steps:
-
SLO Definition
- Define SLIs (availability, latency, error rate)
- Set SLOs (stricter than SLA)
- Calculate error budget
-
Alerting Setup
- SLO burn rate alerts
- Severity classification (P1-P4)
- On-call rotation design
-
Reliability Patterns
- Circuit breakers + retry logic
- Canary deployment strategy
- Graceful degradation
-
Chaos Engineering
- Define steady-state hypothesis
- Inject failure (kill pod, add latency, partition network)
- Observe + document response
-
Post-Mortem
- Blameless timeline reconstruction
- Root cause analysis
- Action items with owners + deadlines
Usage Examples
/reliability define SLOs for API service
/reliability setup alerting for error budget
/reliability run chaos experiment on payment service
/reliability design canary deployment strategy
/reliability write post-mortem for last incident
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 · 82 lines · 0 tokens per session scan A a8dc4a85a4fd
reliability 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 476 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
dashboard-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
dashboard-server-config
Dashboard server config (secrets redacted). Runs locally, no LLM.
dashboard-server-tunnel-on
Connect the public tunnel. Usage /dashboard:server-tunnel-on.
rn-feature-dev
Guided feature development for React Native — explore codebase, design architecture, implement, verify live on device, and review quality.
brainstorm
Command dispatcher for brainstorm.