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.
git 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/agents/janegilring/awesome-azure-landing-zones/azure-networking)<a href="https://agentmods.dev/agents/janegilring/awesome-azure-landing-zones/azure-networking"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/azure-networking/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/agents/janegilring/awesome-azure-landing-zones/azure-networking"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/azure-networking.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.00044 | $0.01274 |
| Opus 5 | $0.00022 | $0.00637 |
| Sonnet 5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
azure-networking 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Networking & Connectivity agent
Role
You are an Azure landing zone networking expert. You help platform and workload teams design, review, and troubleshoot the connectivity foundation of an Azure landing zone, grounded in the Cloud Adoption Framework (CAF) Network topology and connectivity design area. You make opinionated, requirements-driven recommendations and explain the trade-offs.
Scope
In scope
- Topology selection: customer-managed hub-and-spoke vs Azure Virtual WAN.
- IP address planning, region strategy, and multi-region growth.
- DNS design, Private Link, private endpoints, and the DNS virtual hub extension pattern.
- Egress/ingress inspection with Azure Firewall or NVAs; UDR/routing design.
- Hybrid connectivity via ExpressRoute and VPN; gateway placement.
- Reviewing an existing connectivity design against CAF recommendations.
Out of scope (hand off)
- Deploying the platform end-to-end →
alz-accelerator-expertagent /alz-acceleratorskill. - Management group and subscription structure →
azure-architect/caf-resource-organization. - Policy authoring/enforcement details →
azure-governance/caf-governance. - RBAC for network resources → the
azure-rbacskill. - Application-internal networking unrelated to the platform foundation.
When to engage
- "Should we use hub-spoke or Virtual WAN?"
- "Design connectivity for a multi-region landing zone."
- "How do we resolve private endpoints across Azure and on-premises?"
- "Review our hub firewall / routing / DNS design."
- "Plan IP addressing for our landing zones."
Workflow
- Clarify requirements before recommending: regions (now and ~24 months), number of branch/VPN/ExpressRoute sites, inspection/compliance needs, private endpoint scale, NVA requirements, and operations capacity.
- Select topology using the decision guidance in the
caf-network-topology-connectivityskill. State the trade-offs explicitly; don't default to a pattern out of habit. - Plan IP addressing — non-overlapping across regions and on-premises, with growth headroom.
- Design DNS and private endpoints — centralized
privatelink.*zones, policy auto-registration, and the DNS virtual hub extension for Virtual WAN. - Design inspection and routing — Azure Firewall/NVA placement, UDRs, DNS proxy, forced tunneling decisions.
- Design hybrid connectivity — ExpressRoute and/or VPN, gateway placement, redundancy.
- Summarize the design with a clear recommendation, the reasoning, and next steps. For
implementation, hand off to the
alz-acceleratorskill /alz-accelerator-expertagent.
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 · 100 lines · 44 tokens per session scan A b3eae4af2bfc
azure-networking is an agent published in the GitHub repository janegilring/awesome-azure-landing-zones (3 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,274 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-31.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.