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 ricmmartins/azure-sre-agent-skills --skill 02-compliance-governancegit clone --depth 1 https://github.com/ricmmartins/azure-sre-agent-skillsWrote 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/ricmmartins/azure-sre-agent-skills/02-compliance-governance)<a href="https://agentmods.dev/skills/ricmmartins/azure-sre-agent-skills/02-compliance-governance"><img src="https://agentmods.dev/badge/skills/ricmmartins/azure-sre-agent-skills/02-compliance-governance/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/ricmmartins/azure-sre-agent-skills/02-compliance-governance"><img src="https://agentmods.dev/badge/skills/ricmmartins/azure-sre-agent-skills/02-compliance-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.02299 |
| Opus 5 | $0.00026 | $0.01149 |
| Sonnet 5 | $0.00010 | $0.00460 |
| Haiku 4.5 | $0.00005 | $0.00230 |
Grade A, and why
compliance-governance-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 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance & Governance Audit
Purpose
Assess the governance posture of Azure subscriptions by auditing policies, RBAC assignments, tagging standards, resource locks, and regulatory alignment. Produce a compliance scorecard with remediation steps.
CRITICAL formatting rule
Use Unicode emoji characters directly (🟢 🟡 🔴) in ALL output — headers, tables, findings, bullet points, everywhere. NEVER use emoji shortcodes like :red_circle:, :yellow_circle:, :green_circle:, or any :name: syntax. This applies to every section of the report without exception.
When to use this skill
- User asks "are we compliant?"
- User asks about governance, policy violations, or audit readiness
- Pre-audit preparation (SOC2, ISO 27001, HIPAA, etc.)
- Monthly governance review
Pre-check
Confirm with the user:
- Scope: which subscriptions/management groups
- Compliance framework (if any): SOC2, ISO 27001, HIPAA, PCI-DSS, CIS Benchmarks, or general best practices
- Any known exceptions or waivers
Audit procedure
Step 1: Azure Policy compliance
Check overall policy compliance state.
az policy state summarize --query "value[].{policy:policyDefinitionName, nonCompliant:nonCompliantResources}" -o table
- List all non-compliant resources grouped by policy
- Identify policies in "audit" mode that should be "deny"
- Check for orphaned policy assignments (assigned but no effect)
- Verify initiative assignments for regulatory frameworks (CIS, NIST, etc.)
Report:
- Total policies assigned
- % compliant
- Top 5 violated policies with resource count
Step 2: RBAC review
Audit role assignments for least-privilege violations.
az role assignment list --all --query "[].{principal:principalName, role:roleDefinitionName, scope:scope}" -o table
- Owner count: Flag if > 3 Owners at subscription level
- Contributor sprawl: List all Contributor assignments — flag service principals with Contributor when a custom role would suffice
- Classic admins: Check for legacy co-administrators
az role assignment list --include-classic-administrators -o table - Guest users with privileged roles: Flag external identities with Owner/Contributor
- Stale assignments: Cross-reference with sign-in logs — flag principals that haven't signed in for 90+ days
- Custom roles: Review custom role definitions for overly broad permissions (e.g.,
*actions)
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 · 239 lines · 51 tokens per session scan A e770b5e46678
compliance-governance-audit is a skill published in the GitHub repository ricmmartins/azure-sre-agent-skills (70 stars, last pushed 18d ago), licensed MIT. It adds 51 tokens to every session and 2,299 once invoked, about $0.0003 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-30.
Other skills, from other repositories
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
Azure Naming And Tagging
CAF-aligned Azure naming convention and mandatory tags — resource-type abbreviations, region codes, and owner/cost-center/environment/workload tags for cost attribution.
Azure WAF Pillar Review
Azure-specific Well-Architected Framework pillar checklists — reliability, security, cost optimization, operational excellence, performance efficiency — for reviewing Azure infrastructure changes.
Azure CAF Landing Zones
Cloud Adoption Framework governance essentials — management-group hierarchy, subscription design, RBAC scoping, Azure Policy guardrails, and network topology for Azure landing zones.
Azure Identity Design
Entra ID, managed identity, and workload identity federation design for Azure — when to use which, and how to avoid long-lived service-principal secrets.
Azure Security Checklist
Microsoft-recommended Azure security practices — identity, network, data, and monitoring — as a PASS/FAIL/N/A checklist run before any Azure change is proposed for apply.