access-review

access-review is a skill for Claude Code, Codex from Rohit-ATS/Airlock. It costs 33 tokens per session (1,849 once invoked), scanned A, original, MIT.

A method for checking what an access grant really lets a person or service account do. It calculates effective permissions, including access gained through roles and other indirect paths.

In plain words
What is it for?
Use it before writing or reviewing an ACCESSGRANT change to compare newly reachable resources, find the worst reachable access, and check that the grant has an end date.
Why use it?
A permission policy can understate the access it creates, so reading the policy alone may miss sensitive resources or access that never expires.

Skill for Claude CodeCodex

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

Good fit Use it before writing or reviewing an ACCESSGRANT change to compare newly reachable resources, find the worst reachable access, and check that the grant has an end date.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rohit-ats/airlock/access-review
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 Rohit-ATS/Airlock --skill access-review
Clone the repo
git clone --depth 1 https://github.com/Rohit-ATS/Airlock

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 access-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/rohit-ats/airlock/access-review/github.svg)](https://agentmods.dev/skills/rohit-ats/airlock/access-review)
Your own site
<a href="https://agentmods.dev/skills/rohit-ats/airlock/access-review"><img src="https://agentmods.dev/badge/skills/rohit-ats/airlock/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.

agentmods 80×15 button for access-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/rohit-ats/airlock/access-review"><img src="https://agentmods.dev/badge/skills/rohit-ats/airlock/access-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,849 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01849
Opus 5 $0.00016 $0.00924
Sonnet 5 $0.00007 $0.00370
Haiku 4.5 $0.00003 $0.00185

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

Security

Grade A, and why

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 9d 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/access-review/SKILL.md · 201 lines

How it starts

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

Access review

A policy document and an effective permission are not the same thing, and the gap between them is where breaches live. This skill is about closing that gap before a human is asked to sign anything.

The rule that governs everything below: never report what a policy says. Report what a principal can do, computed by simulation against a shadow copy of the account. If you cannot simulate it, say you could not, and do not guess.


1. The three questions

For every principal in the change:

  1. What can they reach after this that they could not reach before? The delta, not the total. An approver cannot judge a 400-line policy document; they can judge four new verbs.
  2. What is the worst thing reachable through this grant? Not the intended use — the maximum. Read access to public.* includes the table nobody remembered was there.
  3. When does it end? A grant with no expiry is refused by policy. There is no such thing as temporary access that nobody scheduled to remove.

2. Effective permissions, not declared ones

Four mechanisms make the declared policy an underestimate. Check each.

Transitive role membership

-- Postgres: everything prod_reader actually inherits, transitively
WITH RECURSIVE m AS (
  SELECT oid, rolname FROM pg_roles WHERE rolname = 'prod_reader'
  UNION
  SELECT r.oid, r.rolname
    FROM pg_auth_members am
    JOIN pg_roles r ON r.oid = am.roleid
    JOIN m ON m.oid = am.member
)
SELECT rolname FROM m;

A role granted a role granted a role is three documents away from the grant you are reviewing. \du shows one level. Recurse.

PUBLIC grants

GRANT ... TO PUBLIC is invisible in a per-role audit and applies to the new principal immediately.

SELECT table_schema, table_name, privilege_type
  FROM information_schema.role_table_grants
 WHERE grantee = 'PUBLIC';

Default privileges

ALTER DEFAULT PRIVILEGES means the grant covers tables that do not exist yet. This is the one people miss: the review passes, and six weeks later a new table containing card data is readable by a role nobody re-reviewed.

Read the full file on GitHub · 201 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. 9d ago First seen · 201 lines · 33 tokens per session scan A 1f3d298000a2

Subscribe to this mod's changes

access-review is a skill published in the GitHub repository Rohit-ATS/Airlock (1 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,849 once invoked, about $0.0002 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-31.