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 agentmods add skills/xobotyi/cc-foundry/networkingnpx skills add xobotyi/cc-foundry --skill networkinggit clone --depth 1 https://github.com/xobotyi/cc-foundryWrote 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/xobotyi/cc-foundry/networking)<a href="https://agentmods.dev/skills/xobotyi/cc-foundry/networking"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/networking.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 | $0.00102 | $0.04757 |
| Opus 5 | $0.00051 | $0.02379 |
| Sonnet 5 | $0.00020 | $0.00951 |
| Haiku 4.5 | $0.00010 | $0.00476 |
Grade A, and why
networking 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 4d 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 -v` -- HTTP/HTTPS connectivity with TLS details How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Networking
Security is a non-negotiable default, not an optional add-on. Every network design decision must account for trust boundaries.
References
Extended configuration examples, comparison tables, and detailed patterns for the rules below live in
${CLAUDE_SKILL_DIR}/references/.
vlan-segmentation.md— VLAN design, trunk/access ports, inter-VLAN policy, Layer 2 security: segment table, firewall rule matrix, hardware requirements, DHCP snooping, DAI, port security, L2 attack mitigationfirewall-rules.md— nftables syntax, OPNsense/pfSense hardening, IPv6 firewall rules: chain types/hooks/priorities, connection tracking, NAT, rate limiting, sets/maps, ICMPv6 policy, dual-stack rulesdns-architecture.md— Pi-hole, AdGuard Home, split-horizon, mDNS, Unbound, DoH/DoT: tool comparison, deployment patterns, Avahi reflector config, recursive vs authoritative, encrypted DNS, IPv6 DNSreverse-proxy.md— Caddy, Traefik, Nginx Proxy Manager, Cloudflare tunnels: Caddyfile examples, Traefik Docker labels, decision matrix, snippet patterns, tunnel patterns, auth proxy integrationvpn-tunnels.md— WireGuard, Tailscale, Headscale, site-to-site, HA with OSPF: config examples, topology comparison, subnet router, hybrid WG+TS, HA failover with BIRD/OSPFtls-certificates.md— Let's Encrypt, ACME, wildcard certs, acme.sh: challenge types, ACME client comparison, certificate storage patterns, TLS configsecurity-hardening.md— SSH, fail2ban, CrowdSec, IDS/IPS, monitoring, hardening: sshd_config, SSH CA, fail2ban vs CrowdSec, Suricata IDS, Prometheus stack, monitoring metrics, IPv6 hardeningauth-proxies.md— Authelia, Authentik, forward auth, SSO patterns: Authelia vs Authentik comparison, ForwardAuth with Traefik/Caddy, SSO/MFA patterns, deployment guidance
VLAN Segmentation
Segment by Trust Level
Separate traffic into functional zones based on trust, not device count:
- Management (VLAN 10): Hypervisors, switches, routers, IPMI/iLO -- highest trust
- Trusted/Lab (VLAN 20): VMs, containers, workstation -- high trust
- IoT (VLAN 30): Smart devices, cameras, sensors -- low trust, restricted
- Guest (VLAN 40): Visitor devices -- zero trust, internet only
- Storage (VLAN 50): NAS, iSCSI, backup targets -- high trust, limited access
- DMZ (VLAN 99): Publicly exposed services -- medium trust, no inward access
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .dev/reference-inventory.json 1.4 KB
- references/auth-proxies.md 4.6 KB
- references/dns-architecture.md 6.1 KB
- references/firewall-rules.md 7.3 KB
- references/reverse-proxy.md 9.1 KB
- references/security-hardening.md 12 KB
- references/tls-certificates.md 3.9 KB
- references/vlan-segmentation.md 5.3 KB
- references/vpn-tunnels.md 8.0 KB
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.
- 4d ago First seen · 450 lines · 102 tokens per session scan A ecd25dd239a2
networking is a skill published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 4,757 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…