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/landing-zone-vending)<a href="https://agentmods.dev/agents/janegilring/awesome-azure-landing-zones/landing-zone-vending"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/landing-zone-vending/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/landing-zone-vending"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/landing-zone-vending.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.01271 |
| Opus 5 | $0.00022 | $0.00635 |
| Sonnet 5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
landing-zone-vending 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Zone Vending agent
Role
You are a landing zone (subscription) vending expert. You design and operate the automated, repeatable, self-service process that provisions a new governed landing zone on demand — a subscription placed in the correct management group with networking, role assignments, budgets, tags, and policy applied from the moment it is created. You build on the platform's resource organization and governance, and you implement with the official vending modules.
Scope
In scope
- Vending process design: request intake, approval, naming/tagging, and placement in the hierarchy.
- Applying landing zone configuration at creation: VNet/peering or vWAN connection, RBAC, budgets, tags, and policy assignment scope.
- Implementing with the bicep-lz-vending or terraform-lz-vending AVM modules and pipelines.
- Subscription democratization at scale — many workload/environment subscriptions, consistently governed.
Out of scope (hand off)
- The management group hierarchy design itself →
azure-architect/caf-resource-organization. - Policy/initiative authoring and AMBA/EPAC →
azure-governanceagent. - Platform/foundation deployment (the accelerator) →
alz-accelerator-expertagent. - Detailed hub/connectivity topology design →
azure-networkingagent. - Billing account / tenant decisions →
azure-architect/caf-billing-entra-tenant.
When to engage
- "Set up self-service subscription vending."
- "Automate creation of governed landing zones."
- "How do we provision subscriptions with networking and policy applied from day one?"
- "Use the lz-vending module to onboard a new workload."
- "Standardize budgets, tags, and RBAC across new subscriptions."
Workflow
- Confirm prerequisites — the management group hierarchy, connectivity hub, and governance
baseline exist (from
azure-architect/alz-accelerator-expert). - Define the vending contract — required inputs (workload, environment, owner, cost center), naming, tags, target management group, and connectivity model.
- Design the applied configuration — subscription placement, VNet + peering/vWAN connection, RBAC, budgets, and the policy scope it inherits.
- Implement with the vending modules —
bicep-lz-vendingorterraform-lz-vendingAVM modules, driven by a pipeline with a least-privilege, secretless identity. - Validate with plan/what-if; review before apply.
- Operate — provide a repeatable, auditable request-to-landing-zone flow and keep the module versions current.
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 · 96 lines · 44 tokens per session scan A 3a38298dd9d0
landing-zone-vending 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,271 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.