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 agentmods add commands/hermeticormus/libresecops-claude-code/azure-sec-auditgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/commands/hermeticormus/libresecops-claude-code/azure-sec-audit)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/azure-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/azure-sec-audit.svg" alt="Measured on agentmods" 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.00000 | $0.01292 |
| Opus 5 | $0.00000 | $0.00646 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
azure-sec-audit 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 6d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/azure-sec-audit
Structured security audit of Azure configuration covering Entra ID, NSGs, storage accounts, Activity Logs, and Azure Policy.
Trigger
Use when you need to:
- Review Azure subscription or tenant configuration for security gaps
- Audit Terraform, ARM, or Bicep templates before deployment
- Evaluate Entra ID security posture (MFA, Conditional Access, PIM)
- Prepare for a CIS Azure Benchmark assessment or SOC 2 audit
- Investigate Azure security posture after organizational changes
Input
One of:
- Live environment: Azure CLI (
az) authenticated with Reader role at subscription level + Global Reader in Entra ID - Infrastructure-as-code: Terraform files (
.tf) using azurerm/azuread providers, ARM templates (.json), or Bicep files (.bicep) - Configuration export: Output from
azcommands, Defender for Cloud exports, Azure Policy compliance reports - Specific scope: Focus area (e.g., "Entra ID only", "networking", "storage accounts")
Process
Phase 1: Identity (Entra ID)
-
Authentication security
- MFA status for all users (
az ad user list+ Conditional Access policies) - Conditional Access policies covering: all users baseline, admin MFA, risky sign-in, device compliance
- Legacy authentication blocked (Conditional Access policy blocking legacy auth protocols)
- Password policy (self-service reset, banned passwords, smart lockout)
- MFA status for all users (
-
Privileged access
- PIM enabled for eligible role assignments (Global Admin, Contributor, Owner)
- Standing admin accounts (permanent vs eligible assignments)
- Emergency access (break-glass) accounts properly configured
- Admin accounts without MFA (critical finding)
-
Service principals & app registrations
- App registrations with client secrets (vs certificate-based authentication)
- Service principals with Owner or Contributor at high scope
- Multi-tenant apps with excessive permissions
- Admin consent grants review
- Managed Identity adoption vs service principal secrets
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.
- 6d ago First seen · 158 lines · 0 tokens per session scan A 209abaa94444
azure-sec-audit is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,292 tokens. 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 commands, from other repositories
build-agent
Build an AI agent on Cloudflare using the Agents SDK.
build-mcp
Build a remote MCP server on Cloudflare using McpAgent.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.