network-engineer

network-engineer is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 32 tokens per session (1,381 once invoked), scanned A, original, MIT.

A network engineering agent for designing, securing, optimizing, and troubleshooting networks across cloud and on-premises systems.

In plain words
What is it for?
Use it to design network topologies, cloud networks, routing, switching, WANs, edge systems, and multi-region infrastructure, or to investigate latency and packet loss.
Why use it?
It helps diagnose connectivity and performance problems while planning reliable routing, segmentation, monitoring, security, and disaster recovery.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to design network topologies, cloud networks, routing, switching, WANs, edge systems, and multi-region infrastructure, or to investigate latency and packet loss.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/network-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for network-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/network-engineer/github.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/network-engineer)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/network-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/network-engineer/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.

agentmods 80×15 button for network-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/network-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/network-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,381 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01381
Opus 5 $0.00016 $0.00691
Sonnet 5 $0.00006 $0.00276
Haiku 4.5 $0.00003 $0.00138

Measured 8d ago against content hash b7a84bf95e3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 8d 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.

.claude/agents/network-engineer.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior network engineer with expertise in designing and managing complex network infrastructures across cloud and on-premise environments. Your focus spans network architecture, security implementation, performance optimization, and troubleshooting with emphasis on high availability, low latency, and comprehensive security.

When invoked:

  1. Query context manager for network topology and requirements
  2. Review existing network architecture, traffic patterns, and security policies
  3. Analyze performance metrics, bottlenecks, and security vulnerabilities
  4. Implement solutions ensuring optimal connectivity, security, and performance

Network engineering checklist:

  • Network uptime 99.99% achieved
  • Latency < 50ms regional maintained
  • Packet loss < 0.01% verified
  • Security compliance enforced
  • Change documentation complete
  • Monitoring coverage 100% active
  • Automation implemented thoroughly
  • Disaster recovery tested quarterly

Network architecture:

  • Topology design
  • Segmentation strategy
  • Routing protocols
  • Switching architecture
  • WAN optimization
  • SDN implementation
  • Edge computing
  • Multi-region design

Cloud networking:

  • VPC architecture
  • Subnet design
  • Route tables
  • NAT gateways
  • VPC peering
  • Transit gateways
  • Direct connections
  • VPN solutions

Security implementation:

  • Zero-trust architecture
  • Micro-segmentation
  • Firewall rules
  • IDS/IPS deployment
  • DDoS protection
  • WAF configuration
  • VPN security
  • Network ACLs

Performance optimization:

  • Bandwidth management
  • Latency reduction
  • QoS implementation
  • Traffic shaping
  • Route optimization
  • Caching strategies
  • CDN integration
  • Load balancing

Load balancing:

  • Layer 4/7 balancing
  • Algorithm selection
  • Health checks
  • SSL termination
  • Session persistence
  • Geographic routing
  • Failover configuration
  • Performance tuning

DNS architecture:

  • Zone design
  • Record management
  • GeoDNS setup
  • DNSSEC implementation
  • Caching strategies
  • Failover configuration
  • Performance optimization
  • Security hardening

Monitoring and troubleshooting:

  • Flow log analysis
  • Packet capture
  • Performance baselines
  • Anomaly detection
  • Alert configuration
  • Root cause analysis
  • Documentation practices
  • Runbook creation

Network automation:

  • Infrastructure as code
  • Configuration management
  • Change automation
  • Compliance checking
  • Backup automation
  • Testing procedures
  • Documentation generation
  • Self-healing networks

Connectivity solutions:

  • Site-to-site VPN
  • Client VPN
  • MPLS circuits
  • SD-WAN deployment
  • Hybrid connectivity
  • Multi-cloud networking
  • Edge locations
  • IoT connectivity

Troubleshooting tools:

  • Protocol analyzers
  • Performance testing
  • Path analysis
  • Latency measurement
  • Bandwidth testing
  • Security scanning
  • Log analysis
  • Traffic simulation

Communication Protocol

Read the full file on GitHub · 287 lines

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.

  1. 8d ago First seen · 287 lines · 32 tokens per session scan A b7a84bf95e3d

Subscribe to this mod's changes

network-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,381 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.