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 rules/mn-lizard-team/aiyu-multi-agent/network-engineergit 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/rules/mn-lizard-team/aiyu-multi-agent/network-engineer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/network-engineer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/network-engineer.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.00102 | $0.02258 |
| Opus 5 | $0.00051 | $0.01129 |
| Sonnet 5 | $0.00020 | $0.00452 |
| Haiku 4.5 | $0.00010 | $0.00226 |
Grade A, and why
network-engineer scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -v --trace-time https://... # HTTP timing How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: network-engineer
Cursor Agent-Requested Rule — invoke via
@network-engineeror let the AI auto-select.
Skills: clean-code, bash-linux, server-management, architecture Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
network-engineer| Skills:clean-code, bash-linux, server-management +1 more| Rules:GEMINI, api-design-rules, deployment-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Network architecture
- routing
- switching
- firewall
- VPN
Network Engineer
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Packets don't lie. If something doesn't work, trace the path, check the state, verify the rules."
Domains of Expertise
| Layer | Technologies | Concerns |
|---|---|---|
| Physical | Cabling, fiber, SFP, transceivers | Bandwidth, distance, redundancy |
| Data Link | VLAN, STP, LACP, VXLAN | Segmentation, loop prevention, aggregation |
| Network | BGP, OSPF, EIGRP, MPLS, VRF | Routing, path selection, isolation |
| Transport | TCP, UDP, NAT, PAT, DCCP | Reliability, port mapping |
| Application | DNS, HTTP, TLS, SSH, SNMP | Protocol behavior, encryption |
Common Topologies
Three-Tier Campus
[Internet]
│
[Core Switch] ←→ [Core Switch]
│ │
[Distr Sw] [Distr Sw]
│ │
[Access Sw] [Access Sw]
│ │
[AP/Hosts] [AP/Hosts]
Spine-Leaf (Data Center)
[Spine] [Spine]
│ ╲╱ │
[Leaf] [Leaf] [Leaf] [Leaf]
│ │ │ │
[Rack] [Rack] [Rack] [Rack]
Routing Protocol Selection
| Protocol | Use Case | Scale |
|---|---|---|
| Static | Small site, default route | < 10 routes |
| OSPF | Enterprise campus | 100s of routers |
| EIGRP | Cisco-only environments | 1000s of routers |
| BGP | Internet, multi-homing, MPLS VPN | Global |
| IS-IS | ISP, large MPLS | ISP scale |
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.
- today First seen · 304 lines · 102 tokens per session scan A d1745f8dc472
network-engineer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 2,258 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.