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-security-checklistgit 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-security-checklist)<a href="https://agentmods.dev/skills/niels-emmer/myace/azure-security-checklist"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-security-checklist/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-security-checklist"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-security-checklist.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.00038 | $0.00786 |
| Opus 5.5 | $0.00015 | $0.00314 |
| Sonnet 5.5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
Azure Security Checklist 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
A fast, consistent pass over an Azure infrastructure change to catch the
Microsoft-recommended security-practice violations that are easy to miss in a
large plan or diff — before it ever reaches the point of asking a human to
approve an apply. This is the Azure-specific companion to iac-expert's
generic iac-security-checklist, adding the Azure constructs (Entra ID,
private endpoints, Key Vault, Defender for Cloud, Azure Policy) that the
generic checklist can't name.
When to use it
Run this against every nontrivial Azure change (new resources, modified network/identity/access configuration) before handing it off for review or requesting apply approval. For a trivial change (a tag fix, a variable rename with no resource impact), a quick skim is enough.
Checklist
Mark each item PASS, FAIL, or N/A. Every FAIL needs either a fix or a
documented exception (see iac-expert's exception-documentation skill)
before the change moves forward.
Identity and access
- Service-to-service auth uses managed identity or workload identity federation, not a service-principal client secret or connection string.
- Any RBAC assignment is scoped to least privilege (resource group/resource, not broad Contributor/Owner) and uses built-in roles where possible.
- Human access is behind Entra ID with MFA and conditional access — no shared accounts, no standing admin credentials in code or config.
- Secrets that must exist live in Key Vault, referenced by ID — never
embedded as a literal in
.tf/.bicep/ARM, a tfvars/parameter file, or a module default.
Network
- No resource has a public IP, public endpoint, or
0.0.0.0/0-equivalent NSG rule unless it's a documented exception. - PaaS services use private endpoints / VNet integration where supported, keeping traffic off the public internet.
- Inter-service traffic that could stay on a private VNet does; NSGs/ASGs default to deny and open only what's needed.
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 · 78 lines · 38 tokens per session scan A 252c2a6de9cc
Azure Security Checklist is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 786 once invoked, about $0.0002 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.