Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/network-engineer.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/network-engineer)<a href="https://agentmods.dev/agents/2ssk/dot-files/network-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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/2ssk/dot-files/network-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.00087 | $0.01447 |
| Opus 5.5 | $0.00035 | $0.00579 |
| Sonnet 5.5 | $0.00017 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00145 |
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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- network-engineer — 91% identical, 95 lines differ
How it starts
The opening of the file, as written. The whole thing — 316 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:
- 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
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.
- 14d ago First seen · 316 lines · 87 tokens per session scan A aa5a85f1b530
network-engineer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 1,447 once invoked, about $0.0003 per session on Opus 5.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-10-02.
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.
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…
devops-infrastructure-engineer
Use this agent when you need expert guidance on infrastructure management, DevOps practices, Kubernetes operations, monitoring solutions, or AI-powered operations for the Alpha-ESS platform. Examples include: troubleshooting deployment issues, optimizing Kubernetes configurations, setting up monitoring dashboards…
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.