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/creategit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWhat 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.00455 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
create 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 3d 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.
What it actually says
/create
Create new application command. Triggers App Builder skill and starts interactive dialogue with user.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `project-planner`** | Skills: `clean-code, app-builder, plan-writing, brainstorming`
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
/create - Create Application
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `project-planner`** | Skills: `clean-code, app-builder, plan-writing, brainstorming`
Task
This command starts a new application creation process.
Steps:
-
Request Analysis
- Understand what the user wants
- If information is missing, use
conversation-managerskill to ask
-
Project Planning
- Use
project-planneragent for task breakdown - Determine tech stack
- Plan file structure
- Create plan file and proceed to building
- Use
-
Application Building (After Approval)
- Orchestrate with
app-builderskill - Coordinate expert agents:
database-architect→ Schemabackend-specialist→ APIfrontend-specialist→ UI
- Orchestrate with
-
Preview
- Start with
auto_preview.pywhen complete - Present URL to user
- Start with
Usage Examples
/create blog site
/create e-commerce app with product listing and cart
/create todo app
/create Instagram clone
/create crm system with customer management
Before Starting
If request is unclear, ask these questions:
- What type of application?
- What are the basic features?
- Who will use it?
Use defaults, add details later.
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.
- 3d ago First seen · 89 lines · 0 tokens per session scan A 4af7f8a2060b
create 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 455 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
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
commit-all
Stage and commit all current changes with a single message. Auto Git Push will pick up and push to origin within 30s.
doctor
Diagnose installation health. Check Node, CDP bridge, rn-fast-runner (iOS), rn-android-runner (Android), maestro-runner, simulators, Metro, CDP, injected helpers, ffmpeg, physical devices, plugin version, Vercel rules sync. Reports what's missing — does NOT modify your project.
goal
Open a /goal contract — write a verifiable manifest before dispatching work.
check
Re-run the quality checks on the current cut.