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/windows)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/windows"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/windows/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/windows"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/windows.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.00435 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
windows 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.
What it actually says
/windows
Windows Server administration, Active Directory, PowerShell automation, Group Policy, and IIS. Used for managing Windows infrastructure, automating with PowerShell, or deploying Windows services.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `windows-administrator`** | Skills: `clean-code, powershell-windows, server-management`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Read the agent's full instructions from
.windsurf/agents/windows-administrator.md(or.cursor/rules/agents/windows-administrator.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/windows — Windows System Administration
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `windows-administrator`** | Skills: `clean-code, powershell-windows, server-management`
Task
Administer Windows Server, Active Directory, and automate with PowerShell.
Steps:
-
Active Directory
- User/group management
- OU structure
- GPO configuration
- Replication
-
PowerShell Automation
- Script modules
- Desired State Configuration
- Scheduled tasks
- Remote management
-
Services
- IIS configuration
- Windows services
- Certificate management
- Event logs
-
Security
- Windows Defender
- Firewall rules
- Auditing
- Patch management
Usage Examples
/windows manage Active Directory users
/windows create PowerShell automation script
/windows configure IIS for web app
/windows setup Group Policy for security
/windows harden Windows Server
/windows automate patch management
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 · 82 lines · 0 tokens per session scan A 407f9c966d64
windows 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 435 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-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.
brainstorm
Command dispatcher for brainstorm.
checklist
Generate a custom checklist for the current feature based on user requirements.