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 janegilring/awesome-azure-landing-zones --skill caf-network-topology-connectivitygit clone --depth 1 https://github.com/janegilring/awesome-azure-landing-zonesWrote 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/janegilring/awesome-azure-landing-zones/caf-network-topology-connectivity)<a href="https://agentmods.dev/skills/janegilring/awesome-azure-landing-zones/caf-network-topology-connectivity"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/caf-network-topology-connectivity/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/janegilring/awesome-azure-landing-zones/caf-network-topology-connectivity"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/caf-network-topology-connectivity.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.00171 | $0.01636 |
| Opus 5.5 | $0.00068 | $0.00654 |
| Sonnet 5.5 | $0.00034 | $0.00327 |
| Haiku 4.5 | $0.00017 | $0.00164 |
Grade A, and why
caf-network-topology-connectivity 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 2mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network topology and connectivity
Overview
Networking is central to almost everything inside an Azure landing zone: it connects workloads to each other, to platform shared services, to external users, and to on-premises infrastructure. This design area sits in the environment group of the eight ALZ design areas because the decisions here shape the platform foundation that every landing zone depends on. Get the topology, IP plan, DNS, and inspection model right early — these are expensive to change later.
In the conceptual ALZ architecture, network resources for the platform live in the Connectivity management group (typically one Connectivity subscription), while workloads run in Corp (private, possibly hybrid-connected) and Online (internet-facing) landing zones.
When to use this skill
- Deciding between hub-and-spoke (customer-managed) and Virtual WAN (Microsoft-managed).
- Planning IP addressing, regions, and multi-region growth.
- Designing DNS, Private Link, and private endpoint name resolution.
- Planning egress/ingress inspection (Azure Firewall / NVA) and forced tunneling.
- Connecting on-premises via ExpressRoute or VPN, and choosing where gateways live.
- Reviewing an existing landing zone's connectivity design against CAF recommendations.
Key concepts
- Connectivity subscription — platform-owned subscription hosting shared network resources (gateways, firewall, DNS, DDoS) in the Connectivity management group.
- Hub-and-spoke — a hub VNet provides shared services and hybrid connectivity; spoke VNets (workloads) peer to it. You manage the hub, routing, and peering yourself.
- Virtual WAN — Microsoft-managed hubs provide built-in any-to-any transitive connectivity and global transit across regions. Hubs only host Microsoft-managed resources (gateways, Azure Firewall via Firewall Manager, route tables, select NVAs).
- Secured virtual hub — a Virtual WAN hub with Azure Firewall managed by Firewall Manager.
- Private endpoint / Private Link — private IP access to Azure PaaS, removing public exposure;
requires deliberate private DNS design to resolve
privatelink.*zones. - Azure DNS Private Resolver — enables on-premises and hub services (e.g. Azure Firewall DNS proxy) to resolve private DNS zones; the recommended building block for DNS at scale.
- UDR (user-defined route) — forces spoke traffic through the hub firewall for inspection.
- Subscription democratization — each workload (or workload-environment) gets its own subscription and VNet; hub-spoke/Virtual WAN is how those VNets share connectivity and inspection.
What ships with it
2 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.
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.
- 2mo ago First seen · 119 lines · 171 tokens per session scan A ae6d775bc36a
caf-network-topology-connectivity is a skill published in the GitHub repository janegilring/awesome-azure-landing-zones (4 stars, last pushed 4mo ago), licensed MIT. It adds 171 tokens to every session and 1,636 once invoked, about $0.0007 per session on Opus 5.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.
caf-network-topology-connectivity compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| caf-network-topology-connectivityjanegilring/awesome-azure-landing-zones | Skill | 4 | 4mo ago | MIT | A | 171 | Claude Code, Codex |
| gke-compute-classesgoogle/skills | Skill | 23k | today | Apache-2.0 | A | 83 | Claude Code, Codex |
| gke-reliabilitygoogle/skills | Skill | 23k | today | Apache-2.0 | A | 85 | Claude Code, Codex |
| gke-workload-securitygoogle/skills | Skill | 23k | today | Apache-2.0 | A | 171 | Claude Code, Codex |
| cloud-architectJeffallan/claude-skills | Skill | 12k | 8d ago | MIT | A | 71 | Claude Code |
| nemo-automodel-launcher-configNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 30 | Claude Code |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 78 | Claude Code |