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 jsgerman-oss/blackrim-nimbus-skills --skill do-networking-and-edgegit clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-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/jsgerman-oss/blackrim-nimbus-skills/do-networking-and-edge)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/do-networking-and-edge"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/do-networking-and-edge/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/jsgerman-oss/blackrim-nimbus-skills/do-networking-and-edge"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/do-networking-and-edge.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.00077 | $0.02901 |
| Opus 5 | $0.00039 | $0.01451 |
| Sonnet 5 | $0.00015 | $0.00580 |
| Haiku 4.5 | $0.00008 | $0.00290 |
Grade A, and why
do-networking-and-edge 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DigitalOcean Networking and Edge
When to use
- Designing a VPC for a new environment or migrating resources into private networking.
- Exposing a service to the internet via a Load Balancer.
- Setting up Floating IPs or Reserved IPs for failover or static entry points.
- Managing DNS zones and records for a domain.
- Writing or auditing Cloud Firewall rules.
- Routing traffic through Spaces CDN for static assets.
- Configuring PTR (reverse DNS) records for mail servers or compliance requirements.
VPC layout — the default
DigitalOcean VPCs are per-region, not global. Every datacenter region has its own VPC namespace.
- One VPC per environment per region. Dev, stage, and prod each get their own VPC. Resources in the same VPC share a private RFC-1918 network; traffic between VPCs or regions is over the public internet unless you use a private tunnel (WireGuard, Tailscale, or a Droplet-based VPN).
- Default VPC: every new DigitalOcean account and project has a default VPC per region. Do not use the default VPC for production — you have no control over its CIDR and cannot rename or segment it meaningfully.
- CIDR planning: choose a
/20or/16range that does not overlap with other VPCs you will ever need to peer or tunnel. Common picks:10.10.0.0/16(prod),10.20.0.0/16(stage),10.30.0.0/16(dev) — adjust to your broader network plan. - Multi-VPC: DigitalOcean does not offer VPC peering as a first-party feature (as of 2026). Cross-VPC connectivity requires a Droplet-based VPN or overlay network (WireGuard, Tailscale). Account for this latency and operational overhead before designing a multi-VPC topology.
- Resource placement: always specify the VPC UUID when creating Droplets, Managed Databases, and DOKS clusters. Resources without an explicit VPC land in the default VPC.
Cloud Firewall
DigitalOcean Cloud Firewall is stateful and applied at the hypervisor layer — it sits between the internet and the Droplet, before any in-guest firewall.
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.
- 12d ago First seen · 138 lines · 77 tokens per session scan A 0e1cd2396f51
do-networking-and-edge is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 77 tokens to every session and 2,901 once invoked, about $0.0004 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 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…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
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".
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…