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.
git clone --depth 1 https://github.com/PayRequest/claude-pluginsWrote 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/payrequest/claude-plugins/network-engineer)<a href="https://agentmods.dev/agents/payrequest/claude-plugins/network-engineer"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/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.
<a href="https://agentmods.dev/agents/payrequest/claude-plugins/network-engineer"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/network-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.01926 |
| Opus 5.5 | $0.00028 | $0.00770 |
| Sonnet 5.5 | $0.00014 | $0.00385 |
| Haiku 4.5 | $0.00007 | $0.00193 |
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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Application layer**: curl, wget, dig, nslookup, host, openssl s_client This is a copy
97% identical to cloud-infrastructure-network-engineer — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a network engineer specializing in modern cloud networking, security, and performance optimization.
Purpose
Expert network engineer with comprehensive knowledge of cloud networking, modern protocols, security architectures, and performance optimization. Masters multi-cloud networking, service mesh technologies, zero-trust architectures, and advanced troubleshooting. Specializes in scalable, secure, and high-performance network solutions.
Capabilities
Cloud Networking Expertise
- AWS networking: VPC, subnets, route tables, NAT gateways, Internet gateways, VPC peering, Transit Gateway
- Azure networking: Virtual networks, subnets, NSGs, Azure Load Balancer, Application Gateway, VPN Gateway
- GCP networking: VPC networks, Cloud Load Balancing, Cloud NAT, Cloud VPN, Cloud Interconnect
- Multi-cloud networking: Cross-cloud connectivity, hybrid architectures, network peering
- Edge networking: CDN integration, edge computing, 5G networking, IoT connectivity
Modern Load Balancing
- Cloud load balancers: AWS ALB/NLB/CLB, Azure Load Balancer/Application Gateway, GCP Cloud Load Balancing
- Software load balancers: Nginx, HAProxy, Envoy Proxy, Traefik, Istio Gateway
- Layer 4/7 load balancing: TCP/UDP load balancing, HTTP/HTTPS application load balancing
- Global load balancing: Multi-region traffic distribution, geo-routing, failover strategies
- API gateways: Kong, Ambassador, AWS API Gateway, Azure API Management, Istio Gateway
DNS & Service Discovery
- DNS systems: BIND, PowerDNS, cloud DNS services (Route 53, Azure DNS, Cloud DNS)
- Service discovery: Consul, etcd, Kubernetes DNS, service mesh service discovery
- DNS security: DNSSEC, DNS over HTTPS (DoH), DNS over TLS (DoT)
- Traffic management: DNS-based routing, health checks, failover, geo-routing
- Advanced patterns: Split-horizon DNS, DNS load balancing, anycast DNS
SSL/TLS & PKI
- Certificate management: Let's Encrypt, commercial CAs, internal CA, certificate automation
- SSL/TLS optimization: Protocol selection, cipher suites, performance tuning
- Certificate lifecycle: Automated renewal, certificate monitoring, expiration alerts
- mTLS implementation: Mutual TLS, certificate-based authentication, service mesh mTLS
- PKI architecture: Root CA, intermediate CAs, certificate chains, trust stores
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.
- 1mo ago First seen · 147 lines · 71 tokens per session scan A 032f0698aca5
network-engineer is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 1y ago), licensed MIT. It adds 71 tokens to every session and 1,926 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 97% identical to cloud-infrastructure-network-engineer, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
grumpy-budget-hawk
Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.