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 srnichols/plan-forge --skill azure-sweepgit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/azure-sweep)<a href="https://agentmods.dev/skills/srnichols/plan-forge/azure-sweep"><img src="https://agentmods.dev/badge/skills/srnichols/plan-forge/azure-sweep.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.02142 |
| Opus 5 | $0.00000 | $0.01071 |
| Sonnet 5 | $0.00000 | $0.00428 |
| Haiku 4.5 | $0.00000 | $0.00214 |
Grade A, and why
azure-sweep 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 7d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
Description
Executes a prioritised compliance sweep across WAF, CAF, Landing Zone, Policy, Org Rules, Resource Graph, Telemetry, and Remediation layers. Outputs a structured findings report with Bicep, Terraform, and CLI remediation code.
When to Use
- Before a production deployment
- After an environment is provisioned
- During quarterly compliance reviews
- When Advisor or Defender alerts spike
- When onboarding an existing subscription into CAF governance
Prerequisites
| Requirement | Check |
|---|---|
| Azure CLI authenticated | az account show |
| Correct subscription selected | az account set --subscription <id> |
| Resource Graph extension installed | az extension add --name resource-graph |
| Instruction files present | presets/azure-iac/.github/instructions/ |
| Org rules initialised (optional) | .github/instructions/org-rules.instructions.md |
Steps
Step 0 — Scope & Setup
Confirm scope before running:
# Set scope variables
$subscriptionId = (az account show --query id -o tsv)
$rg = "<resource-group>" # or "ALL" for subscription-wide
Write-Host "Sweeping subscription: $subscriptionId"
Write-Host "Resource group scope: $rg"
Step 1 — WAF Layer
# Fetch Azure Advisor WAF recommendations
az advisor recommendation list `
--filter "Category eq 'HighAvailability' or Category eq 'Security' or Category eq 'Cost' or Category eq 'OperationalExcellence' or Category eq 'Performance'" `
--output json | ConvertFrom-Json | `
Select-Object category, impact, shortDescription, resourceMetadata
Pass gate: No CRITICAL Advisor items in Reliability or Security pillars.
Step 2 — CAF Layer
# Management group placement
az account management-group list --output table
# Tag compliance per resource group
az group list --query "[].{RG:name, Tags:tags}" --output json | ConvertFrom-Json | `
Where-Object { -not $_.Tags.Environment -or -not $_.Tags.Owner -or -not $_.Tags.CostCenter }
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.
- 7d ago First seen · 257 lines · 0 tokens per session scan A 876efe7025c8
azure-sweep is a skill published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,142 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 skills, from other repositories
ring:creating-grafana-dashboards
Authoring Grafana dashboards for Go services instrumented with lib-observability telemetry (tracing, metrics, log), plus a reference mode for RED/USE panel patterns and Grafonnet templates. Sweep mode inventories telemetry, runs PM deliberation on themes/SLIs/alerts, authors Grafonnet libsonnet compiled to JSON, and…
ring:migrating-to-lib-systemplane
Migrating Lerian Go services from .env/YAML operational knobs (log levels, feature flags, rate limits, timeouts) to the lib-systemplane hot-reloadable runtime config client, wiring the migration-only make systemplane-ddl pipeline (runtime DDL forbidden in v1.6.0+). Orchestrates an 11-gate cycle dispatching…
ring:creating-helm-charts
Creating Helm charts to Lerian conventions via ring:helm: standardized chart structure, full env-var coverage from .env.example, security defaults (runAsNonRoot, readOnlyRootFilesystem), ClusterIP-only services, and health probes; validates helm lint and template render. Use when creating, modifying, or reviewing a…
web-security-check
Use this agent to validate the live deployed surface of a web application before production promotion.
production-orchestrator
Use this agent for end-to-end PRD-to-production pipeline execution with zero-tolerance validation, compliance gates, and rollback capability.
sre
Use this agent for site reliability engineering - incident response, SLOs/SLIs, monitoring, chaos engineering, runbooks, and system reliability.