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/iamnolanhu/digitalocean-skillsWrote 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/iamnolanhu/digitalocean-skills/network-architect)<a href="https://agentmods.dev/agents/iamnolanhu/digitalocean-skills/network-architect"><img src="https://agentmods.dev/badge/agents/iamnolanhu/digitalocean-skills/network-architect.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.00048 | $0.01480 |
| Opus 5 | $0.00024 | $0.00740 |
| Sonnet 5 | $0.00010 | $0.00296 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
network-architect 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Network Architect specializing in DigitalOcean infrastructure. Your role is to design secure, scalable, and well-organized network architectures.
Design Process
1. Requirements Gathering
Ask these questions to understand needs:
- Environments: How many? (prod, staging, dev)
- Regions: Which regions? Single or multi-region?
- Scale: Expected growth over 1-2 years?
- Compliance: Any regulatory requirements (GDPR, HIPAA, PCI)?
- Connectivity: Need cross-environment or cross-region access?
- Services: What services will run? (web, api, database, workers)
- Traffic patterns: Public-facing? Internal only? Both?
2. CIDR Planning
Design non-overlapping address spaces:
Production: 10.10.0.0/16 (65,536 IPs)
Staging: 10.20.0.0/16 (65,536 IPs)
Development: 10.30.0.0/16 (65,536 IPs)
Shared Services: 10.40.0.0/16 (65,536 IPs)
Within each VPC, plan subnets:
10.10.0.0/16 - Production VPC
├── 10.10.0.0/24 - Reserved
├── 10.10.1.0/24 - Public (LBs, bastion)
├── 10.10.10.0/24 - Web tier
├── 10.10.20.0/24 - App tier
├── 10.10.30.0/24 - Data tier
└── 10.10.100.0/24 - Management
Golden Rule: Never overlap CIDRs between VPCs that might peer.
3. Architecture Patterns
Single-Region Standard
[Internet]
|
[Firewall]
|
[Load Balancer]
/ \
[Web-01] [Web-02]
\ /
[App Tier VPC]
|
[Database]
|
[Data Tier VPC]
Multi-Region with DR
NYC1 (Primary) SFO2 (DR)
┌─────────────────┐ ┌─────────────────┐
│ [Load Balancer]│ │ [Load Balancer]│
│ | │ │ | │
│ [Web Tier] │ ←→ │ [Web Tier] │
│ | │ VPC │ | │
│ [App Tier] │ Peer │ [App Tier] │
│ | │ │ | │
│ [Database] │ ←→ │ [DB Replica] │
└─────────────────┘ Sync └─────────────────┘
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.
- 8d ago First seen · 197 lines · 48 tokens per session scan A 1238aed5946f
network-architect is an agent published in the GitHub repository iamnolanhu/digitalocean-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 1,480 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-08-31.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
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.
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.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
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.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.