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 niels-emmer/myace --skill azure-caf-landing-zonesgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/azure-caf-landing-zones)<a href="https://agentmods.dev/skills/niels-emmer/myace/azure-caf-landing-zones"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-caf-landing-zones/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/niels-emmer/myace/azure-caf-landing-zones"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-caf-landing-zones.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.00036 | $0.00965 |
| Opus 5.5 | $0.00014 | $0.00386 |
| Sonnet 5.5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
Azure CAF Landing Zones 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
The Microsoft Cloud Adoption Framework (CAF) is the set of practices for governing Azure at scale. This skill covers the governance essentials you need to design a landing zone that is secure, auditable, and cost-attributable — management-group hierarchy, subscription design, RBAC scoping, Azure Policy guardrails, and network topology. It deliberately does not reproduce the full landing-zone accelerator; the accelerator is a reference for the complete, opinionated implementation, while this skill is the decision layer you apply to any Azure environment.
When to use it
When designing or reviewing an Azure environment's structure — a new subscription, a management-group reorganization, a policy/guardrail change, or a network-topology decision. Also before scaffolding a new workload into an existing landing zone, to confirm it fits the established pattern.
Management-group hierarchy
- Separate platform (management, connectivity, identity) from workload management groups, so governance applied at the platform level inherits down without entangling workload-specific policy.
- Keep the hierarchy shallow and meaningful — a handful of levels, each with a clear purpose, not a deep tree that mirrors the org chart.
- Apply policy and RBAC at the highest level where it's uniformly correct, and
let it inherit; override only where a genuine exception exists (and document
it per
iac-expert'sexception-documentationskill).
Subscription design
- Use subscriptions as scale units and trust boundaries, not cost centers (cost attribution belongs to tags, not subscription boundaries).
- Group subscriptions by environment/workload boundary (e.g. a
prod/nonprodsplit, or one per major workload) so blast radius and policy scope stay manageable. - Avoid a single subscription for everything, and avoid one subscription per microservice — both extremes make governance either impossible or unmanageable.
RBAC scoping
- Assign roles at the narrowest effective scope — resource group or resource, not subscription-wide, unless the role genuinely applies everywhere.
- Prefer built-in roles over custom ones; when a custom role is unavoidable, grant only the specific actions needed.
- Use managed identity / workload identity for service-to-service access
(see the
azure-identityskill), never a human account or a long-lived service-principal secret. - Never grant Owner/Contributor broadly as a shortcut — least privilege is the baseline.
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.
- 1mo ago First seen · 91 lines · 36 tokens per session scan A 93620c285d22
Azure CAF Landing Zones is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 965 once invoked, about $0.0001 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.
Other skills, from other repositories
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
ai-foundry-posture-check
Assess security, reliability, and cost posture of Azure OpenAI and Microsoft Foundry deployments. Detects critical anti-patterns: API keys instead of Managed Identity, public endpoints without firewall, disabled content filtering, missing diagnostic settings, deprecated model versions, over-provisioned PTU, absence of…
digital-native-governance-check
Assess Azure governance maturity for Digital Natives and startups. Detects the most common anti-patterns from the "Digital Natives on Azure" series: incomplete Service Health alerts, flat subscription topology without Management Groups, excessive RBAC (everyone is Owner), missing budget alerts, no Managed Identity…
well-architected-review
Run a Well-Architected Framework (WAF) review against Azure resources in scope. Use when asked about best practices, architecture review, WAF assessment, or pillar compliance (Reliability, Security, Cost, Operational Excellence, Performance Efficiency).
compliance-governance-audit
Audit Azure environment for compliance and governance posture. Checks Azure Policy, RBAC, tagging, resource locks, naming conventions, and regulatory alignment. Use when asked about compliance, governance, audit readiness, or policy violations.