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 alz-acceleratorgit 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/alz-accelerator)<a href="https://agentmods.dev/skills/janegilring/awesome-azure-landing-zones/alz-accelerator"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/alz-accelerator/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/alz-accelerator"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/alz-accelerator.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.00213 | $0.01587 |
| Opus 5 | $0.00106 | $0.00794 |
| Sonnet 5 | $0.00043 | $0.00317 |
| Haiku 4.5 | $0.00021 | $0.00159 |
Grade A, and why
alz-accelerator 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ALZ Accelerator
Overview
The Azure Landing Zones Accelerator turns the conceptual ALZ architecture into a deployable
platform: management groups, policies, the platform subscriptions (Connectivity, Identity,
Management), and the connectivity foundation, delivered as infrastructure as code. It ships in three
IaC flavors — Terraform and Bicep (both on Azure Verified Modules), plus the original
ALZ-Bicep "classic" framework. This skill is the implementation layer: it assumes the
architecture is already decided (the caf-* design-area skills) and focuses on how to bootstrap
and deploy it. Tool-specific detail lives in references/.
When to use this skill
- Choosing between the Terraform, Bicep (AVM), and Bicep classic accelerators.
- Running the bootstrap (repos, pipelines, deployment identity) before deploying the platform.
- Deploying and tailoring the platform / starter modules through the accelerator phases.
- Planning a migration from ALZ-Bicep classic → Bicep (AVM).
- Keeping an accelerator deployment up to date with upstream module/AVM/policy releases.
Key concepts
- IaC variants:
terraform—Azure/alz-terraform-accelerator, using AVM for Terraform (the platform landing zone module).bicep— the current Bicep accelerator built on Azure Verified Modules.bicep-classic— the originalAzure/ALZ-Bicepframework (still supported; migrate to AVM Bicep when ready).
- Phases — the accelerator follows a phased path: planning → prerequisites → getting started
→ deployment. See
references/phases.md. - Bootstrap — one-time setup of the toolchain (Git repo, CI/CD, service connection, and a
least-privilege deployment identity using OIDC/workload identity federation) that precedes
platform deployment. See
references/bootstrap.md. - Starter / platform module — the opinionated module that deploys the management groups, policies, and platform resources; you tailor it to your design.
- Azure Verified Modules (AVM) — Microsoft-verified building blocks. Reached via the
bicepMCP server (list_avm_metadata) and the Terraform Registry; there is no separate AVM server. - Azure Landing Zones Library — shared definitions (archetypes, policies) consumed by the accelerators.
What ships with it
5 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.
- 12d ago First seen · 109 lines · 213 tokens per session scan A 6a79f9cd78aa
alz-accelerator is a skill published in the GitHub repository janegilring/awesome-azure-landing-zones (3 stars, last pushed 2mo ago), licensed MIT. It adds 213 tokens to every session and 1,587 once invoked, about $0.0011 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…