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/cloudgit 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.00509 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 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 2d 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.
- 2d 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 (7 stars, last pushed 3mo 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
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.
deploy
Deploy the application to production.
goal
Open a /goal contract — write a verifiable manifest before dispatching work.