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 skills add iamnolanhu/digitalocean-skills --skill designing-vpcsgit 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/skills/iamnolanhu/digitalocean-skills/designing-vpcs)<a href="https://agentmods.dev/skills/iamnolanhu/digitalocean-skills/designing-vpcs"><img src="https://agentmods.dev/badge/skills/iamnolanhu/digitalocean-skills/designing-vpcs/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/skills/iamnolanhu/digitalocean-skills/designing-vpcs"><img src="https://agentmods.dev/badge/skills/iamnolanhu/digitalocean-skills/designing-vpcs.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.00052 | $0.01489 |
| Opus 5 | $0.00026 | $0.00745 |
| Sonnet 5 | $0.00010 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
designing-vpcs 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 11d 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.
curl -s -H "Authorization: Bearer $DIGITALOCEAN_API_TOKEN" \ 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.
Designing VPCs
Design secure, scalable VPC architectures following network segmentation best practices.
When to Use
- Setting up new infrastructure
- Isolating environments (prod/staging/dev)
- Connecting services across regions
- Planning network architecture
- User mentions: "VPC", "private network", "isolate", "network design"
VPC Architecture Principles
- Segment by environment - Production isolated from non-production
- Segment by tier - Web, app, data in logical groups
- Minimal peering - Only peer what's necessary
- Document CIDR blocks - Avoid overlaps for future peering
CIDR Planning
Single-Region Design
10.10.0.0/16 - Production VPC (65,536 IPs)
10.10.1.0/24 - Public tier (load balancers)
10.10.10.0/24 - Web tier
10.10.20.0/24 - App tier
10.10.30.0/24 - Data tier
10.20.0.0/16 - Staging VPC
10.20.1.0/24 - Public
10.20.10.0/24 - Web tier
10.20.20.0/24 - App tier
10.30.0.0/16 - Development VPC
10.30.0.0/20 - All resources (4,096 IPs)
Multi-Region Design
Region: NYC1
10.10.0.0/16 - Production
10.20.0.0/16 - Staging
Region: SFO2
10.110.0.0/16 - Production (DR)
Region: AMS3
10.210.0.0/16 - EU Production
Critical: Never overlap CIDR blocks between VPCs you might peer.
The Process
1. Inventory
vpc-list (existing VPCs)
droplet-list (what needs VPC access)
2. Design Questions
- How many environments?
- Which regions?
- Need cross-region connectivity?
- Compliance requirements (data residency)?
- Expected growth?
3. Create VPCs
vpc-create:
Name: vpc-<region>-<environment>
Region: nyc1
IPRange: 10.10.0.0/16
Description: "Production VPC in NYC1"
4. VPC Peering (if needed)
vpc-peering-create:
Name: peer-prod-nyc1-sfo2
VpcIds: [<vpc1-id>, <vpc2-id>]
VPC Peering Patterns
Hub-and-Spoke
[Shared Services VPC]
/ | \
/ | \
[Prod VPC] [Staging] [Dev VPC]
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.
- 11d ago First seen · 197 lines · 52 tokens per session scan A b9ac1dc5cfe9
designing-vpcs is a skill published in the GitHub repository iamnolanhu/digitalocean-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 1,489 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…