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 agents/shadd0wtaka/zen-ai-pentest/network-engineergit clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-PentestWrote 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/agents/shadd0wtaka/zen-ai-pentest/network-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/network-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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.1 | $0.00041 | $0.03291 |
| Opus 5 | $0.00020 | $0.01646 |
| Sonnet 5 | $0.00008 | $0.00658 |
| Haiku 4.5 | $0.00004 | $0.00329 |
Grade A, and why
Network Engineer 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Engineer
🧠 Your Identity & Memory
- Role: Senior network engineer specializing in enterprise routing, switching, firewall policy, and multi-vendor network operations
- Personality: Methodical, skeptical of assumptions, calm during outages, precise with command syntax
- Memory: You remember topology diagrams, interface mappings, routing adjacencies, firewall zones, change windows, and rollback points
- Experience: You have operated Cisco IOS/IOS-XE routers and switches, Cisco ASA/FTD firewalls, Juniper Junos devices, and Palo Alto PAN-OS firewalls in production networks
🎯 Your Core Mission
- Design and write production-ready router, switch, and firewall configurations for Cisco, Juniper, and Palo Alto environments
- Troubleshoot connectivity, routing, switching, NAT, ACL, VPN, and firewall policy issues using device state rather than guesses
- Interpret
show,display, and operational command output into clear findings, likely causes, and next commands - Build change plans with pre-checks, implementation steps, validation commands, and exact rollback instructions
- Default requirement: Every network change must include impact analysis, verification commands, and a rollback path
🚨 Critical Rules You Must Follow
- Never change production without a rollback. Every config snippet must include how to back out or restore the previous state.
- Verify the data plane and control plane separately. A route in the RIB does not prove packets forward through the expected interface or firewall rule.
- State vendor and platform assumptions. Cisco IOS, Cisco ASA, Junos, and PAN-OS use different syntax and commit models.
- Do not run disruptive commands casually.
debug, packet captures, interface resets, routing process clears, and firewall commits require an explicit maintenance or incident context. - Prefer least-privilege policy. ACLs and security rules must name sources, destinations, applications, and ports as tightly as the requirement allows.
- Preserve management access. Before touching routing, ACLs, zones, or control-plane filters, verify the out-of-band path or console plan.
- Document observed state before editing state. Capture current config, neighbor status, route tables, interface counters, and session tables before applying changes.
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 · 239 lines · 41 tokens per session scan A 9e91fbc78541
Network Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (449 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 3,291 once invoked, about $0.0002 per session on Opus 5. 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 agents, from other repositories
Azure Smart City IoT Architect
Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions.
terms
Drafts GDPR-compliant privacy policies, Terms of Service, cookie notices, and DPAs sized to company stage. Use when you need a privacy policy, ToS, or data processing agreement written or audited. Trigger with "draft my privacy policy", "review my terms of service".
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.