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/debug)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/debug"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/debug/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/debug"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/debug.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.00597 |
| Opus 5.5 | $0.00000 | $0.00239 |
| Sonnet 5.5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
debug 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug
Debugging command. Activates DEBUG mode for systematic problem investigation.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `debugger`** | Skills: `clean-code, systematic-debugging`
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
/debug - Systematic Problem Investigation
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `debugger`** | Skills: `clean-code, systematic-debugging`
Purpose
This command activates DEBUG mode for systematic investigation of issues, errors, or unexpected behavior.
Behavior
When /debug is triggered:
-
Gather information
- Error message
- Reproduction steps
- Expected vs actual behavior
- Recent changes
-
Form hypotheses
- List possible causes
- Order by likelihood
-
Investigate systematically
- Test each hypothesis
- Check logs, data flow
- Use elimination method
-
Fix and prevent
- Apply fix
- Explain root cause
- Add prevention measures
Output Format
## 🔍 Debug: [Issue]
### 1. Symptom
[What's happening]
### 2. Information Gathered
- Error: `[error message]`
- File: `[filepath]`
- Line: [line number]
### 3. Hypotheses
1. ❓ [Most likely cause]
2. ❓ [Second possibility]
3. ❓ [Less likely cause]
### 4. Investigation
**Testing hypothesis 1:**
[What I checked] → [Result]
**Testing hypothesis 2:**
[What I checked] → [Result]
### 5. Root Cause
🎯 **[Explanation of why this happened]**
### 6. Fix
```[language]
// Before
[broken code]
// After
[fixed code]
7. Prevention
🛡️ [How to prevent this in the future]
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.
- 1mo ago First seen · 133 lines · 0 tokens per session scan A 032415fad400
debug is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (8 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 597 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
debug-screen
Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers parallel evidence from all layers and applies a targeted fix.
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
debug-help
Structure debugging requests to efficiently identify and resolve issues.
errors
Error handling review — silent failure detection, catch block analysis, error logging.
checklist
Generate a custom checklist for the current feature based on user requirements.