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/cloud)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/cloud"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/cloud/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/cloud"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/cloud.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.00509 |
| Opus 5.5 | $0.00000 | $0.00204 |
| Sonnet 5.5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
cloud 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cloud
Cloud architecture design, multi-cloud strategy, and infrastructure as code. Used for designing cloud-native systems, selecting managed services, and cost-aware architecture.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `cloud-architect`** | Skills: `clean-code, architecture, server-management, deployment-procedures`
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/cloud-architect.md(or.cursor/rules/agents/cloud-architect.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/cloud — Cloud Architecture Design
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `cloud-architect`** | Skills: `clean-code, architecture, server-management, deployment-procedures`
Task
Design cloud architecture, select services, and plan infrastructure as code.
Steps:
-
Requirements Analysis
- Workload type (web, ML, batch, real-time)
- Scale expectations (users, data, traffic)
- Compliance constraints (data residency, encryption)
- Budget constraints
-
Architecture Design
- Select cloud provider(s)
- Choose compute (VM, container, serverless)
- Design database layer (SQL, NoSQL, cache)
- Plan networking (VPC, CDN, load balancing)
-
High Availability
- Multi-AZ deployment
- Disaster recovery strategy (RPO/RTO)
- Failover mechanisms
-
Infrastructure as Code
- Terraform module structure
- Remote state backend
- CI/CD integration
-
Cost Estimation
- Right-sizing recommendations
- Reserved vs on-demand strategy
- Cost monitoring setup
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 · 84 lines · 0 tokens per session scan A d5eed56b4be0
cloud 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 509 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.