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 ivegamsft/basecoat --skill azure-policy-auditgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/azure-policy-audit)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/azure-policy-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/azure-policy-audit/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/ivegamsft/basecoat/azure-policy-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/azure-policy-audit.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.00059 | $0.00330 |
| Opus 5 | $0.00030 | $0.00165 |
| Sonnet 5 | $0.00012 | $0.00066 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
azure-policy-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.
What it actually says
Azure Policy Audit Skill
Review Azure governance controls for coverage, remediation completeness, exemption hygiene, and compliance traceability.
USE FOR
- Auditing Azure Policy definitions and initiatives
- Checking remediation tasks and DeployIfNotExists coverage
- Reviewing exemption usage, expiry, and justification quality
- Verifying compliance reports reflect the intended scope
DO NOT USE FOR
- Application business logic
- RBAC-only access questions
- Generic troubleshooting without a policy concern
- Infrastructure changes that do not affect policy
Workflow
- Confirm the intended control and the scope it should cover.
- Check the effect, parameters, and initiative composition for correctness.
- Review exemptions for justification, expiry, and drift risk.
- Validate remediation and reporting paths are complete.
- Summarize gaps with severity, evidence, and next steps.
Output
Return:
- Verdict: pass, pass with notes, or request changes
- Findings with severity and evidence
- Coverage gaps or false-positive risk
- Suggested remediation or policy update
Related Agent
Use with policy-as-code-compliance agent.
What ships with it
1 file 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.
- 6d ago First seen · 51 lines · 59 tokens per session scan A 6bdff448ca9e
azure-policy-audit is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 330 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-09-03.
Other skills, from other repositories
monitoring-and-alerting
Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert…
launch-runbook
Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers…
azure-integrations
Azure deployment for web apps — Static Web Apps, App Service, Blob Storage, Bicep/ARM, GitHub Actions CI/CD. Use when deploying Next.js/Vite to Azure or configuring Azure resources for full-stack apps.
microsoft-development
Microsoft docs lookup, code samples, and SDK reference for Azure, .NET, Microsoft 365, Windows, and Power Platform via Microsoft Learn MCP. Use for API reference or official MS documentation retrieval.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
cloud-design-patterns
Choose and compare cloud design patterns for distributed systems. Use when reviewing architecture, selecting workload patterns, or mapping reliability, performance, messaging, security, and migration concerns to concrete design options.