A set of instructions for reviewing and designing identity and access management: the systems that decide who users and services are and what they may access. It covers cloud permissions, identity providers, application authorization, and sign-in federation.

Use it to audit existing access, design identity controls for a new project, or plan a migration to consolidated sign-in or single sign-on.

It helps find excessive permissions, weak identity setups, and gaps in access control. It also provides patterns for building a new setup or moving between identity systems.

iam-audit — Cursor rule for Cursor 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.

Clone the repo

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

Made for: Cursor.

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/rules/briiirussell/cybersecurity-skills/iam-audit/github.svg)](https://agentmods.dev/rules/briiirussell/cybersecurity-skills/iam-audit)

Your own site

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

Per session 173 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,924 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.

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.00173	$0.02924
Opus 5	$0.00086	$0.01462
Sonnet 5	$0.00035	$0.00585
Haiku 4.5	$0.00017	$0.00292

Measured 11d ago against content hash 8f6de79039a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 11d 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.

adapters/cursor/iam-audit.mdc · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 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 · 174 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.

11d ago First seen · 174 lines · 173 tokens per session scan A 8f6de79039a7

Subscribe to this mod's changes

iam-audit is a cursor rule published in the GitHub repository briiirussell/cybersecurity-skills (387 stars, last pushed 3mo ago), licensed MIT. It adds 173 tokens to every session and 2,924 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

iam-audit

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

IAM Audit — Identity & Access Management Review and Design

Mode 1 — Audit existing IAM

Cloud provider IAM

What this file has done since we first saw it

Other cursor rules, from other repositories

ponytail

angular-20

dev-standard

cli-error-handling

prefer-direct-imports-over-module-mocks

control-plane-descriptors