network-topology

network-topology is a skill for Claude Code from sethdford/claude-skills. It costs 42 tokens per session (688 once invoked), scanned A, original, MIT.

A guide for designing a virtual private cloud, an isolated network in a cloud provider. It covers subnets, firewall rules, load balancers, DNS, protection against traffic attacks, and backup routing when a component fails.

In plain words
What is it for?
Use it to plan web, application, and database network layers; control which services can connect; distribute traffic; configure domain routing; and plan failover.
Why use it?
It helps turn application needs, compliance requirements, and traffic expectations into a segmented and safer network design.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the infrastructure-design plugin — 8 skills shipped together

Good fit Use it to plan web, application, and database network layers; control which services can connect; distribute traffic; configure domain routing; and plan failover.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sethdford/claude-skills/network-topology
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.

Any agent
npx skills add sethdford/claude-skills --skill network-topology
Clone the repo
git clone --depth 1 https://github.com/sethdford/claude-skills

Made for: Claude Code.

Or install infrastructure-design, the plugin that ships this one along with the rest of its 8 skills.

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-topology

README.md
[![agentmods](https://agentmods.dev/badge/skills/sethdford/claude-skills/network-topology/github.svg)](https://agentmods.dev/skills/sethdford/claude-skills/network-topology)
Your own site
<a href="https://agentmods.dev/skills/sethdford/claude-skills/network-topology"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/network-topology/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-topology

Your own site · 80×15
<a href="https://agentmods.dev/skills/sethdford/claude-skills/network-topology"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/network-topology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 688 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.00042 $0.00688
Opus 5 $0.00021 $0.00344
Sonnet 5 $0.00008 $0.00138
Haiku 4.5 $0.00004 $0.00069

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

Security

Grade A, and why

network-topology 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 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.

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.

architect/infrastructure-design/skills/network-topology/SKILL.md · 48 lines

How it starts

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

Network Topology

Design secure, scalable network architecture with proper segmentation, load balancing, and failover.

Context

You are designing network infrastructure. Plan VPCs, subnets, security groups, load balancers, DNS, DDoS protection. Read application requirements, compliance needs, and expected traffic patterns.

Domain Context

Based on network architecture best practices (AWS VPC, GCP VPC):

  • VPC: Virtual private cloud; isolated network environment. Multiple subnets for segmentation.
  • Subnets: Public (NAT to internet) and private (no direct internet). Separate database tier from web tier.
  • Security Groups: Stateful firewall rules. Default-deny, whitelist only needed ports.
  • Load Balancing: ALB for HTTP/HTTPS, NLB for TCP/UDP. Distribute traffic across instances.
  • DNS: Route 53 for DNS with health checks and failover routing

Instructions

  1. Design VPC: CIDR block (10.0.0.0/16 typical). Public subnets in AZ-1 and AZ-2 for web tier. Private subnets for database tier. NAT Gateway for outbound access from private.

  2. Segment with Security Groups: Web tier: allow 80/443. App tier: allow traffic from web only. Database tier: allow traffic from app tier only. Principle of least privilege.

  3. Plan Load Balancing: Application Load Balancer (ALB) for web traffic; routes by hostname/path. Network Load Balancer (NLB) for high performance, millions of RPS.

  4. Set Up DNS: Route 53 routes users to nearest region or healthy endpoint. Health checks detect failures; failover to standby. Support multiple A records for multi-region.

  5. Implement DDoS Protection: CloudFlare or Shield Standard for volumetric attacks. WAF for application-layer attacks (SQL injection, XSS). Rate limiting for API abuse.

Anti-Patterns

  • Single Subnet for Everything: All servers in one subnet. Result: hard to enforce policies, lateral movement risk. Guard: Segment by tier; use security groups for access control.
  • Overly Permissive Security Groups: Allow 0.0.0.0/0 (anywhere) on all ports. Result: security risk. Guard: Default-deny; whitelist specific ports/IPs.
  • No Health Checks: Load balancer routes to dead instance. Result: user errors. Guard: Health checks detect failures; remove from load balancer.
  • Ignoring DDoS: Assume no one will attack. Result: downtime during attack. Guard: DDoS protection layers (WAF, rate limiting, CDN); plan capacity for spikes.

Read the full file on GitHub · 48 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. 11d ago First seen · 48 lines · 42 tokens per session scan A 728f705090f0

Subscribe to this mod's changes

network-topology is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 688 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-30.

Related

Other skills, from other repositories

enterprise-agent-ops

Operate long-lived agent workloads with observability, security boundaries, and lifecycle management.

majiang213/OpenClaw-MAS · 21 tokens

multi-tenant-architecture

Designs tenant isolation, hostname routing, custom-domain lifecycle, and plan limits on Cloudflare or Vercel. Use when asked to "isolate tenant data", "support custom domains", "build a white-label platform", or assess PSL registration. For general module structure use codebase-architecture; for SEO content use seo.

mblode/agent-skills · 72 tokens

discovery-patterns

Configure ServiceNow Discovery — schedules, IP ranges, credential affinities, MID Server assignment, custom probes/sensors, identification rules, and run-status monitoring on discovery tables.

serac-labs/serac · 40 tokens

cloud-hosting-expert

Expert guide for deploying SaaS applications with multiple entry points on modern edge and serverless platforms like Vercel and Cloudflare / Panduan ahli untuk mendeploy aplikasi SaaS dengan multiple entry points di platform edge dan serverless modern seperti Vercel dan Cloudflare.

roedyrustam/vibes-plug · 61 tokens

deno-deploy

Use when deploying Deno apps to production, asking about Deno Deploy, or working with deno deploy CLI commands. Covers deployment workflows, environment variables, KV database access, custom domains, the --tunnel flag for local development, and the deno deploy command reference.

denoland/skills · 64 tokens

aws-cdk

Create and review Java AWS CDK v2 infrastructure code organized with the BCE (Boundary-Control-Entity) pattern — scaffold the project, wire the app entry point, pin regions in a central Stacks interface, model business components named after AWS services, and keep stacks thin over reusable constructs. Use whenever…

AdamBien/airails · 0 tokens