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/migrategit 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/migrate)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/migrate"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/migrate.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 | $0.00000 | $0.00501 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
migrate 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate
Activate migration-specialist for database migrations, system migrations, framework upgrades, and codebase modernization.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `migration-specialist`** | Skills: `clean-code, architecture, database-design, refactoring-patterns, systematic-debugging +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
/migrate - Migration & Upgrades
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `migration-specialist`** | Skills: `clean-code, architecture, database-design, refactoring-patterns, systematic-debugging +1 more`
Task
Load .windsurf/agents/migration-specialist.md and execute migration tasks with specialist context.
Guidelines
- Read
.windsurf/agents/migration-specialist.mdfor full agent instructions - Apply migration principles:
- Reversibility first: Every migration step must have a rollback
- Incremental over big-bang: Small, verifiable steps beat massive cutover
- Data integrity is sacred: Validate before, during, and after
- Test in production-like conditions: Staging is not production
- Communicate everything: Migration plans, timelines, risks, and status
- Follow required skills from frontmatter for domain-specific rules
Verification Scripts
python3 .windsurf/skills/database-design/scripts/schema_validator.py .
python3 .windsurf/skills/lint-and-validate/scripts/lint_runner.py .
python3 .windsurf/skills/testing-patterns/scripts/test_runner.py .
Examples
/migrate upgrade Next.js 14 to 15 with breaking changes
/migrate plan zero-downtime database schema change for users table
/migrate JavaScript to TypeScript incrementally
/migrate MySQL to PostgreSQL with data validation
/migrate monolith to microservices using strangler fig pattern
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.
- 4d ago First seen · 72 lines · 0 tokens per session scan A eadf94a7e2a2
migrate 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 501 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
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.
brainstorm
Command dispatcher for brainstorm.
plan
Command dispatcher for plan.
goal
Open a /goal contract — write a verifiable manifest before dispatching work.
qos-workspace
Browse the workspace files and agent logs of a completed QOS task.