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 zmustafa/AzureSupportAgent --skill access-reviewgit clone --depth 1 https://github.com/zmustafa/AzureSupportAgentWrote 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/zmustafa/azuresupportagent/access-review)<a href="https://agentmods.dev/skills/zmustafa/azuresupportagent/access-review"><img src="https://agentmods.dev/badge/skills/zmustafa/azuresupportagent/access-review/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/zmustafa/azuresupportagent/access-review"><img src="https://agentmods.dev/badge/skills/zmustafa/azuresupportagent/access-review.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.00033 | $0.00212 |
| Opus 5.5 | $0.00013 | $0.00085 |
| Sonnet 5.5 | $0.00007 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
Azure and Entra access review 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.
What it actually says
Azure and Entra access review
- Start from the cached IAM access model so direct, inherited, group-derived, ownership, PIM, control-plane, and data-plane paths are evaluated together.
- Resolve the exact principal and scope before answering who can do what.
- Distinguish active, eligible, and activated access; never call eligibility standing access.
- Include deny assignments, notActions, scope inheritance, and unresolved ABAC conditions.
- Use
why_does_principal_have_accessbefore proposing removal andsimulate_revokebefore a real revocation. - Report stale or absent scan coverage explicitly.
- Recommend least-privilege changes with the assignment id and blast radius, but keep writes behind the approval policy.
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 · 16 lines · 33 tokens per session scan A a901f2646965
Azure and Entra access review is a skill published in the GitHub repository zmustafa/AzureSupportAgent (47 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 212 once invoked, about $0.0001 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-30.
Other skills, from other repositories
applying-azure-cost-guardrails
Applies Azure cost guardrails to a deployment — consumption-priced SKUs, Container Apps that really scale to zero (cooldownPeriod, wake vectors, CI resurrection), SQL Serverless vs flat Basic, Log Analytics dailyQuotaGb cap, Storage lifecycle rules, free tiers, and the Azure-native backstop (Consumption budget +…
securing-azure-sql-and-storage-with-managed-identity
Moves an Azure Functions app's RUNTIME data-plane auth off the stored SQL password and storage account key onto the compute's system-assigned managed identity — Entra token auth for Azure SQL and user-delegation SAS for Blob Storage. Ships flag-gated (default OFF, old paths byte-identical) so cutover is a no-op until…
deploying-azure-container-apps
Deploys Docker containers to Azure Container Apps with scale-to-zero that actually scales to zero — cooldownPeriod kept at 300s, KEDA cron warm windows instead of minReplicas 1, Jobs for anything async, and the retirement checklist that stops CI resurrecting a deleted app. Covers multi-container sidecars, shared…
deploying-azure-static-web-apps
Deploys React + Azure Functions apps to Azure Static Web Apps with managed API functions, including the CommonJS / index.ts import / route-registration gotchas that make new functions 404 silently. Provides the SWA Bicep module, staticwebapp.config.json routing + security headers, and the API entrypoint convention.…
deploying-fc1-flex-consumption-functions
Deploys standalone Azure Function Apps on Flex Consumption (FC1) for workloads SWA managed functions can't handle — timer triggers, queue triggers, AI workloads, long-running operations, or when you need managed identity / Key Vault references (SWA managed functions support neither). Provisions via Bicep or ARM REST…
orchestrating-azure-deployments
Routes Azure web app work (scaffold, deploy, troubleshoot, evolve) to the right Azure Lean Stack sub-skill. Built around branch-per-environment CI/CD where each git branch maps to one isolated Azure resource group via OIDC. Use when building or deploying a new Azure app, setting up GitHub Actions for Azure…