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/deploy)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/deploy"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/deploy/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/deploy"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/deploy.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.01018 |
| Opus 5.5 | $0.00000 | $0.00407 |
| Sonnet 5.5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
deploy 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy
Deployment command for production releases. Pre-flight checks and deployment execution.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `devops-engineer`** | Skills: `clean-code, deployment-procedures, server-management, powershell-windows +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
/deploy - Production Deployment
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `devops-engineer`** | Skills: `clean-code, deployment-procedures, server-management, powershell-windows +1 more`
Purpose
This command handles production deployment with pre-flight checks, deployment execution, and verification.
Sub-commands
/deploy - Interactive deployment wizard
/deploy check - Run pre-deployment checks only
/deploy preview - Deploy to preview/staging
/deploy production - Deploy to production
/deploy rollback - Rollback to previous version
Pre-Deployment Checklist
Before any deployment:
## 🚀 Pre-Deploy Checklist
### Code Quality
- [ ] No TypeScript errors (`npx tsc --noEmit`)
- [ ] ESLint passing (`npx eslint .`)
- [ ] All tests passing (`npm test`)
### Security
- [ ] No hardcoded secrets
- [ ] Environment variables documented
- [ ] Dependencies audited (`npm audit`)
### Performance
- [ ] Bundle size acceptable
- [ ] No console.log statements
- [ ] Images optimized
### Documentation
- [ ] README updated
- [ ] CHANGELOG updated
- [ ] API docs current
### Ready to deploy? (y/n)
Deployment Flow
┌─────────────────┐
│ /deploy │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Pre-flight │
│ checks │
└────────┬────────┘
│
Pass? ──No──► Fix issues
│
Yes
│
▼
┌─────────────────┐
│ Build │
│ application │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Deploy to │
│ platform │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Health check │
│ & verify │
└────────┬────────┘
│
▼
┌─────────────────┐
│ ✅ Complete │
└─────────────────┘
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 · 206 lines · 0 tokens per session scan A 6b08c42f477a
deploy 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 1,018 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-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
dashboard-server-config
Dashboard server config (secrets redacted). Runs locally, no LLM.
dashboard-server-tunnel-on
Connect the public tunnel. Usage /dashboard:server-tunnel-on.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
plan
Command dispatcher for plan.