A review and design workflow for identity and access management (IAM), the rules that control who can sign in and what they can access. It covers cloud providers, identity services, application permissions, and federated login systems.

Use it to audit, design, or migrate AWS, GCP, Azure, Okta, Auth0, Google Workspace, application roles, and other access systems.

It helps find excessive permissions, weak access controls, and gaps in an existing identity setup. It can also guide a new design or a move between identity providers and single sign-on (SSO) systems.

iam-audit — Skill for Claude Code by briiirussell

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 briiirussell/cybersecurity-skills --skill iam-audit

Clone the repo

git clone --depth 1 https://github.com/briiirussell/cybersecurity-skills

Made for: Claude Code.

Or install cybersecurity-skills, the plugin that ships this one along with the rest of its 28 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/briiirussell/cybersecurity-skills/iam-audit/github.svg)](https://agentmods.dev/skills/briiirussell/cybersecurity-skills/iam-audit)

Your own site

<a href="https://agentmods.dev/skills/briiirussell/cybersecurity-skills/iam-audit"><img src="https://agentmods.dev/badge/skills/briiirussell/cybersecurity-skills/iam-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/briiirussell/cybersecurity-skills/iam-audit"><img src="https://agentmods.dev/badge/skills/briiirussell/cybersecurity-skills/iam-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 177 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,940 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 warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Privilege Escalation · line 108
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00177	$0.02940
Opus 5	$0.00088	$0.01470
Sonnet 5	$0.00035	$0.00588
Haiku 4.5	$0.00018	$0.00294

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

Security

Grade A, and why

iam-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 12d 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.

skills/iam-audit/SKILL.md · 175 lines

How it starts

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

IAM Audit — Identity & Access Management Review and Design

Cover the identity and access layer end-to-end: audit existing setup, design from scratch, plan migrations, and codify the patterns most teams get wrong. This is the consultant-style skill — not just "what's misconfigured" but "what should this look like."

Three modes — pick the one that matches the engagement:

Audit — review what's already deployed, find privilege creep and gaps
Design — greenfield IAM for a new project or new identity provider
Migrate — consolidate multiple identity providers, federate access, move to SSO

Cross-references: cloud-audit for the cloud-provider audit (broader than IAM), container-audit for K8s RBAC and ServiceAccounts (orchestration-layer identity).

Mode 1 — Audit existing IAM

Cloud provider IAM

AWS:

IAM users with console access — should be zero in mature setups (use SSO/Identity Center)
IAM users with permanent access keys — every one is a credential rotation problem; replace with role assumption via SSO or IAM Roles Anywhere
Permissions boundaries set on every role that can create roles (prevents privilege escalation via iam:CreateRole + iam:AttachRolePolicy)
AdministratorAccess policy attachments — flag every one and justify
Wildcard Action: "*" or Resource: "*" outside of break-glass roles
Cross-account trust policies — Principal: { AWS: "*" } is open to the world; should be specific account IDs with optional aws:PrincipalOrgID condition
IMDSv2 enforced — MetadataOptions.HttpTokens: required on every EC2 launch template
Service-linked roles audited — they bypass normal restrictions
Run: aws accessanalyzer list-findings, aws iam generate-credential-report, aws iam get-account-authorization-details

GCP:

roles/owner and roles/editor are too broad — replace with custom roles or fine-grained roles/*Admin
Service account keys downloaded (projects.serviceAccounts.keys.create) — should be zero; use Workload Identity Federation
Service accounts with iam.serviceAccountTokenCreator on themselves = self-impersonation = privilege escalation
Org-level vs project-level bindings — over-scoped bindings at the org level are silent privilege grants to every project
allUsers / allAuthenticatedUsers bindings on any sensitive resource
Run: gcloud asset analyze-iam-policy, gcloud policy-intelligence query-activity, Recommender API

Read the full file on GitHub · 175 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.

12d ago First seen · 175 lines · 177 tokens per session scan A 73b49edd474a

Subscribe to this mod's changes

iam-audit is a skill published in the GitHub repository briiirussell/cybersecurity-skills (391 stars, last pushed 3mo ago), licensed MIT. It adds 177 tokens to every session and 2,940 once invoked, about $0.0009 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.

Security

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens