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/networkgit 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/network)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/network"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/network.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00486 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
network 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 3d 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.
/network
Network architecture, routing, switching, firewall design, VPN, and load balancing. Used for designing LAN/WAN topologies, configuring network devices, or troubleshooting connectivity.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `network-engineer`** | Skills: `clean-code, bash-linux, server-management, architecture`
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/network-engineer.md(or.cursor/rules/agents/network-engineer.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/network — Network Engineering
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `network-engineer`** | Skills: `clean-code, bash-linux, server-management, architecture`
Task
Design, configure, and troubleshoot network infrastructure.
Steps:
-
Topology Design
- Physical layout (cabling, devices)
- Logical layout (VLANs, subnets, routing)
- Redundancy and failover
-
IP Addressing
- Subnet planning (CIDR)
- DHCP scopes
- DNS resolution
-
Routing
- Protocol selection (OSPF, BGP, static)
- Route summarization
- Path redundancy
-
Security
- Firewall rules (ACL, zone-based)
- VPN (site-to-site, remote access)
- Network segmentation
-
Load Balancing
- L4 vs L7
- Algorithm selection
- Health checks
Usage Examples
/network design office LAN with VLANs
/network configure BGP between two sites
/network setup WireGuard VPN
/network design firewall rules for DMZ
/network configure Nginx load balancer
/network troubleshoot packet loss
/network design SD-WAN for branches
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.
- 3d ago First seen · 84 lines · 0 tokens per session scan A 0d31c79efdd8
network 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 486 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.
goal
Open a /goal contract — write a verifiable manifest before dispatching work.
argos
설계 산출물 대비 구현 검증 — 준공검사 감리 (아르고스).
minos
QA 시나리오 기반 Playwright 테스트 자동 생성 + 브라우저 탐색 QA + fix-until-pass 루프 (미노스).
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.