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/incident-response)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/incident-response"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/incident-response.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.00485 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
incident-response 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/incident-response
Security incident response — breach detection, containment, forensics, recovery, and post-mortem. Used when investigating suspected compromise or data breach.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `incident-responder`** | Skills: `vulnerability-scanner, bash-linux, server-management`
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
/incident-response — Security Incident Handler
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `incident-responder`** | Skills: `vulnerability-scanner, bash-linux, server-management`
Task
Respond to security incidents with discipline. Detect, contain, eradicate, recover, learn.
Steps:
-
Detection & Triage
- Identify affected systems, data, users
- Preserve evidence (logs, memory, disk)
- Classify severity: P0 (active) to P3 (suspicious)
-
Containment
- Isolate compromised instances
- Revoke tokens, disable accounts
- Patch exploited vulnerability
-
Eradication
- Remove attacker access (backdoors, malware)
- Verify no persistence remains
-
Recovery
- Restore from clean backups (verify integrity)
- Gradual re-enablement with monitoring
-
Post-Mortem
- Timeline reconstruction
- Root cause (5 Whys)
- Preventive measures
Usage Examples
/incident-response suspected data breach
/incident-response leaked API key
/incident-response ransomware detected
/incident-response unauthorized access
/incident-response compromised account
Caution
- Do NOT panic — measure twice, cut once
- Preserve evidence before remediation
- Communicate through proper channels (legal/PR if needed)
- Document everything — compliance may require proof
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.
- 7d ago First seen · 89 lines · 0 tokens per session scan A 05a736fd51ab
incident-response 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 485 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-session-abort-all
Abort multiple running sessions (asks which). Usage /dashboard:session-abort-all.
dashboard-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
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.