azure-rbac

azure-rbac is a skill for Claude Code, Codex from jonathan-vella/apex-accelerator. It costs 98 tokens per session (1,169 once invoked), scanned A, original, MIT.

A guide for selecting Azure role-based access control, or RBAC, permissions for an identity. RBAC controls which actions a person or service identity can perform on Azure resources.

In plain words
What is it for?
Use it to choose built-in or custom roles, set the correct scope, and generate role-assignment code for Azure CLI, Bicep, or Terraform.
Why use it?
It helps grant only the access that is needed and avoids giving an identity broader permissions than necessary.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to choose built-in or custom roles, set the correct scope, and generate role-assignment code for Azure CLI, Bicep, or Terraform.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonathan-vella/apex-accelerator/azure-rbac
Install

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.

Any agent
npx skills add jonathan-vella/apex-accelerator --skill azure-rbac
Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for azure-rbac

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-rbac/github.svg)](https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-rbac)
Your own site
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-rbac"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-rbac/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.

agentmods 80×15 button for azure-rbac

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-rbac"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-rbac.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00098 $0.01169
Opus 5 $0.00049 $0.00584
Sonnet 5 $0.00020 $0.00234
Haiku 4.5 $0.00010 $0.00117

Measured 6d ago against content hash d4d2b84d795a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

azure-rbac 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.

.github/skills/azure-rbac/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure RBAC Skill

Find the minimal built-in Azure role that grants the requested permissions to an identity, then generate the az role assignment create CLI and a Bicep Microsoft.Authorization/roleAssignments snippet. Custom roles only when no built-in fits.

Rules

  • Least privilege first — prefer the most narrowly-scoped built-in role that satisfies the permissions; only define a custom role when no built-in fits
  • Role assignment scope matters — prefer resource-level or resource-group scope over subscription scope
  • Discover roles via mcp_azure-mcp_documentation — invoke with command: "microsoft_docs_search" to query for built-in role definitions before generating any CLI or Bicep
  • Verify with az role definition list — cross-check the discovered role against the live Azure RBAC catalogue
  • Use guid() in Bicep for Microsoft.Authorization/roleAssignments names so assignments are idempotent across re-deploys; set principalType: 'ServicePrincipal' for managed identities
  • Granting roles requires elevated permission — see Prerequisites for Granting Roles below
  • Out of scope: deploying resources (use azure-deploy), security audits (use azure-compliance)

Steps

  1. Identify the operation — what action does the identity need (read storage, manage keys, deploy resources, etc.)?

  2. Search Microsoft docs — invoke mcp_azure-mcp_documentation with command: "microsoft_docs_search" and a query such as "Azure built-in role <operation>" (e.g., "Azure built-in role read blob storage"); collect candidate role names + role IDs

  3. Verify against the live catalogueaz role definition list --query "[?roleName=='<RoleName>'].{name:roleName,id:name,actions:permissions[0].actions}" -o table

  4. If no built-in fits — scaffold a custom role definition with only the required actions / dataActions:

    cat > custom-role.json <<'JSON'
    {
      "Name": "<CustomRoleName>",
      "Description": "<purpose>",
      "Actions": ["<provider>/<resource>/<action>"],
      "DataActions": [],
      "AssignableScopes": ["/subscriptions/<sub-id>"]
    }
    JSON
    az role definition create --role-definition custom-role.json
    

Read the full file on GitHub · 102 lines

Changes

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.

  1. 6d ago First seen · 102 lines · 98 tokens per session scan A d4d2b84d795a

Subscribe to this mod's changes

azure-rbac is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 1,169 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-09-03.