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 skills/microsoft/sre-agent/rbac-auditnpx skills add microsoft/sre-agent --skill rbac-auditgit clone --depth 1 https://github.com/microsoft/sre-agentWrote 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/microsoft/sre-agent/rbac-audit)<a href="https://agentmods.dev/skills/microsoft/sre-agent/rbac-audit"><img src="https://agentmods.dev/badge/skills/microsoft/sre-agent/rbac-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 | $0.00100 | $0.01865 |
| Opus 5 | $0.00050 | $0.00932 |
| Sonnet 5 | $0.00020 | $0.00373 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
rbac-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 4d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zava Learning — RBAC / Least-Privilege & Access-Usage Audit
Resource Group: @@RG@@. Read-only audit — never create, modify, or remove a role assignment.
This is a weekly governance review of who can do what here, and whether they actually use it. The
goal is real least-privilege hygiene: surface over-privileged identities, direct (ungoverned)
assignments, and standing access that has gone unused so a human can clean it up.
Identity naming policy (governance reports name their subjects)
The principals under audit (their display name / UPN / objectId and role) are the subject of this
report — show them; an RBAC finding that hides the identity is useless. This is NOT the learner-PII
the redaction standard protects. Still apply SearchMemory("zava-redaction") redact() to strip any
secrets, tokens, credentials, or learner/customer PII that happen to appear, and never print
secret values — but DO name the admins, service principals, and groups being audited.
Where the names come from (do NOT call Microsoft Graph): take the identity name from the
principalName field that az role assignment list already returns, plus principalType. Do not
run az ad user/group/sp list|show or az rest https://graph.microsoft.com/... to resolve names or
look up guest/enabled status — the SRE Agent's managed identity has no Graph directory-read
permission, so those calls fail with Insufficient privileges AND are gated as PendingAuthorization,
which would stall this unattended weekly run. If a principalName is blank, identify that principal by
its principalId (objectId) + principalType and note "display name unavailable (directory lookup not
permitted)". A UPN containing #EXT# (when present in principalName) still indicates a guest.
1. Enumerate the real assignments effective on the RG
- All assignments scoped at or above the RG (this includes subscription/management-group inheritance —
most access here is inherited):
az role assignment list --scope /subscriptions/<sub>/resourceGroups/@@RG@@ --include-inherited -o json. - For each: capture
principalName,principalType(User / Group / ServicePrincipal),roleDefinitionName,scope,description, andcreatedOnwhere present. These fields are sufficient — everything you need to name and classify a principal is already in this output; no follow-up directory calls.
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.
- 4d ago First seen · 103 lines · 100 tokens per session scan A a31640482a8e
rbac-audit is a skill published in the GitHub repository microsoft/sre-agent (149 stars, last pushed 10d ago), licensed MIT. It adds 100 tokens to every session and 1,865 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…