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/status)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/status"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/status/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/status"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/status.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.00541 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
status 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/status
Display agent and project status. Progress tracking and status board.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `explorer-agent`** | Skills: `clean-code, architecture, plan-writing, brainstorming +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
/status - Show Status
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `explorer-agent`** | Skills: `clean-code, architecture, plan-writing, brainstorming +1 more`
Task
Show current project and agent status.
What It Shows
-
Project Info
- Project name and path
- Tech stack
- Current features
-
Agent Status Board
- Which agents are running
- Which tasks are completed
- Pending work
-
File Statistics
- Files created count
- Files modified count
-
Preview Status
- Is server running
- URL
- Health check
Example Output
=== Project Status ===
📁 Project: my-ecommerce
📂 Path: C:/projects/my-ecommerce
🏷️ Type: nextjs-ecommerce
📊 Status: active
🔧 Tech Stack:
Framework: next.js
Database: postgresql
Auth: clerk
Payment: stripe
✅ Features (5):
• product-listing
• cart
• checkout
• user-auth
• order-history
⏳ Pending (2):
• admin-panel
• email-notifications
📄 Files: 73 created, 12 modified
=== Agent Status ===
✅ database-architect → Completed
✅ backend-specialist → Completed
🔄 frontend-specialist → Dashboard components (60%)
⏳ test-engineer → Waiting
=== Preview ===
🌐 URL: http://localhost:3000
💚 Health: OK
Technical
Status uses these scripts:
python3 .windsurf/scripts/session_manager.py statuspython3 .windsurf/scripts/auto_preview.py status
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.
- 5d ago First seen · 116 lines · 0 tokens per session scan A 23ae652acf82
status 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 541 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-09-03.
Other commands, from other repositories
dashboard-proposal-detach
Detach the OpenSpec change from a session. Usage /dashboard:proposal-detach.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
qos-workspace
Browse the workspace files and agent logs of a completed QOS task.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
r-status
Display a structured overview of project health: plan progress, phase outcomes, governance freshness, and recent activity.