What is check-permission-matrix?

A documentation audit that compares an RBAC permission matrix with the roles and permissions defined in code. RBAC, or role-based access control, gives users permissions according to their roles.

Use it to check roles, permissions, grants, and global permissions, and to report every mismatch between the code and the Markdown document.

It finds cases where the documentation says users can or cannot do something different from the application. This prevents the permission guide from becoming an unreliable source of information.

How bayesimpact/bayes-platform configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bayesimpact/bayes-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bayesimpact/bayes-platform/main/.claude/skills/check-permission-matrix/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bayesimpact/bayes-platform

Made for: Claude Code.

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/bayesimpact/bayes-platform/check-permission-matrix/github.svg)](https://agentmods.dev/skills/bayesimpact/bayes-platform/check-permission-matrix)

Your own site

<a href="https://agentmods.dev/skills/bayesimpact/bayes-platform/check-permission-matrix"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/check-permission-matrix/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/bayesimpact/bayes-platform/check-permission-matrix"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/check-permission-matrix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 613 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.00046	$0.00613
Opus 5.5	$0.00018	$0.00245
Sonnet 5.5	$0.00009	$0.00123
Haiku 4.5	$0.00005	$0.00061

Measured 20d ago against content hash a0c35852d125, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

check-permission-matrix 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 20d 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.

.claude/skills/check-permission-matrix/SKILL.md · 31 lines

How it starts

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

Verify that docs/rbac-permission-matrix.md is an exact mirror of the RBAC catalog in code.

Steps

Read the two code sources of truth:
- packages/api-contracts/src/rbac/permissions.ts — permission string constants (the only declaration) and every member of the GlobalPermission union.
- apps/api/src/domains/rbac/rbac.constants.ts — extract every role key and its granted permissions from every *_ROLE_PERMISSIONS map: ORGANIZATION_ROLE_PERMISSIONS, PROJECT_ROLE_PERMISSIONS, AGENT_ROLE_PERMISSIONS and REVIEW_CAMPAIGN_ROLE_PERMISSIONS. Search the file for _ROLE_PERMISSIONS = { so a new map is not missed. Also read PROJECT_PERMISSIONS_FROM_REVIEW_CAMPAIGN (the project keys a campaign role gives on the campaign's project), REVIEW_CAMPAIGN_STATUSES_GIVING_PROJECT_PERMISSIONS (the campaign statuses under which each campaign role gives them), RESOURCE_TYPE_PERMISSIONS_MAP (the keys a parent passes down to each child type) and PARENT_RESOURCE_TYPE_MAP (the parents of each type). Permission constants such as TRACE_READ_PERMISSION are imported from the contracts file; resolve them to their string values. The API file must not redeclare those strings.
Read docs/rbac-permission-matrix.md and parse each table into (permission, role) → granted/not-granted pairs. A cell such as ✅ while active is a grant with a campaign status condition.
Compare both directions and collect mismatches:
- Role in code but missing from the doc (or the reverse)
- Permission granted in code but unchecked/missing in the doc (or the reverse)
- GlobalPermission union member absent from the "Global roles" table
- A key granted on a review campaign role that is neither a review_campaign.* key nor in PROJECT_PERMISSIONS_FROM_REVIEW_CAMPAIGN
- A campaign status statement in the doc, in prose or in a table cell, that differs from REVIEW_CAMPAIGN_STATUSES_GIVING_PROJECT_PERMISSIONS
- A statement that a key passes down from a parent, or does not, that differs from RESOURCE_TYPE_PERMISSIONS_MAP and PARENT_RESOURCE_TYPE_MAP
Report the results:

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

20d ago Changed · +3 lines a0c35852d125
1mo ago Changed 2e3806647b95
1mo ago First seen · 28 lines · 46 tokens per session scan A 59ca389c9751

Subscribe to this mod's changes

check-permission-matrix is a skill published in the GitHub repository bayesimpact/bayes-platform (23 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 613 once invoked, about $0.0002 per session on Opus 5.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-14.

Code review Security

check-permission-matrix next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
check-permission-matrixbayesimpact/bayes-platform	Skill	23	yesterday	MIT	A	46	Claude Code
autoreviewopenclaw/clawhub	Skill	9.5k	yesterday	MIT	A	17	Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	6d ago	MIT	A	115	Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermes	Skill	5.2k	yesterday	MIT	A	48	Claude Code, Codex
revdiff-planumputun/revdiff	Skill	945	yesterday	MIT	A	84	Claude Code
explore-unknownsdzhng/skills	Skill	1.4k	2d ago	MIT	A	162	Claude Code, Codex
re0-mergeLilMGenius/paperthin	Skill	1.4k	4d ago	MIT	A	70	Claude Code

bayes-platform: Skill for Claude Code