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 azure-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/azure-networking-and-edge)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/azure-networking-and-edge"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-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/azure-networking-and-edge"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-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.00070 | $0.02812 |
| Opus 5 | $0.00035 | $0.01406 |
| Sonnet 5 | $0.00014 | $0.00562 |
| Haiku 4.5 | $0.00007 | $0.00281 |
Grade A, and why
azure-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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Networking and Edge
When to use
- Designing a new VNet for a subscription or workload.
- Exposing an internal service to the internet or to another VNet / subscription.
- Tuning TLS, WAF, or DDoS posture at the edge.
- Auditing east-west connectivity (VNet peering, Private Link, VPN Gateway, ExpressRoute).
- Tracing latency or cross-region egress cost.
VNet layout — the boring default
- One VNet per environment (dev / stage / prod). Hub-spoke topology when you have more than two workload VNets or any compliance pressure — the hub VNet is the cheapest blast-radius boundary Azure gives you for centralized inspection.
- Address space:
/16per VNet./24or/22per subnet — leave headroom; Azure reserves 5 addresses per subnet. - Subnets per design (not one-per-AZ like AWS — Azure subnets span all AZs in a region):
snet-appgw— Application Gateway; requires a dedicated subnet, minimum/26.snet-app— application workloads (App Service VNet integration, Container Apps, AKS user pool).snet-data— private endpoints for storage, databases, caches.snet-mgmt— Azure Bastion or management jump services.
- IPv6 dual-stack if the workload has large-scale egress or cross-region replication needs; Azure public IPv4 charges apply for any static public IP.
- NSG Flow Logs to a Storage Account (cheap) and optionally to Traffic Analytics via Log Analytics for visibility.
Subnet, NSG, and route table discipline
- NSGs: stateful, the primary per-subnet control. Associate one NSG per subnet; reference Azure Service Tags (
AzureLoadBalancer,AzureMonitor,Storage.EastUS) instead of raw CIDRs for intra-Azure traffic. - Default-deny posture: NSG inbound rule
65000 DenyAllInBoundis implicit. Add explicit allows for required traffic only. Never add an inbound allow for port 22 or 3389 to0.0.0.0/0. - Application security groups (ASGs): group VMs and pods by role (ASG
asg-app,asg-db) and reference ASGs in NSG rules for readable intent without CIDR fragility. - UDRs (User Defined Routes): force-tunnel
0.0.0.0/0via Azure Firewall in the hub for any subnet that should not have direct internet egress.
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 · 147 lines · 70 tokens per session scan A e8c0338ef82b
azure-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 70 tokens to every session and 2,812 once invoked, about $0.0003 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…