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 commands/mn-lizard-team/aiyu-multi-agent/legacygit 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/legacy)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/legacy"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/legacy.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.00461 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
legacy 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/legacy
Analyze legacy code, understand undocumented systems, and plan modernization. Used for refactoring brownfield code, reverse engineering, and technical archaeology.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `code-archaeologist`** | Skills: `clean-code, refactoring-patterns, code-review-checklist`
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
/legacy - Legacy Code Analysis
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `code-archaeologist`** | Skills: `clean-code, refactoring-patterns, code-review-checklist`
Task
Analyze legacy, messy, or undocumented code. Understand intent, identify risks, and plan safe modernization.
Steps:
-
Discovery
- Read target files
- Map dependencies and mutations
- Identify global state and circular references
-
Characterization Testing
- Capture current output as "Golden Master"
- Verify test passes on messy code
-
Analysis Report
- Estimated age (syntax patterns)
- Inputs / Outputs / Side effects
- Risk factors (global state, magic numbers, tight coupling)
-
Refactoring Plan
- Extract methods
- Rename variables
- Add guard clauses
- Gradual migration (Strangler Fig pattern)
Usage Examples
/legacy analyze this 500-line function
/legacy refactor jQuery to React
/legacy modernize Python 2 code
/legacy understand this spaghetti codebase
/legacy add types to untyped JavaScript
Caution
- Never refactor without tests or fallback
- Use Strangler Fig: wrap, don't rewrite
- Document every assumption
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 · 85 lines · 0 tokens per session scan A b4747a521007
legacy 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 461 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.
brainstorm
Command dispatcher for brainstorm.
errors
Error handling review — silent failure detection, catch block analysis, error logging.
verify
Verify the current work and report only blockers, regressions, and gaps.
fix-fast
Compressed SDLC path for small bug fixes only — collapses Plan + Analyze + Design into a single mini-gate. Not for new builds or change requests.