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.
git clone --depth 1 https://github.com/bayesimpact/bayes-platformWrote 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.
[](https://agentmods.dev/rules/bayesimpact/bayes-platform/permission-matrix)<a href="https://agentmods.dev/rules/bayesimpact/bayes-platform/permission-matrix"><img src="https://agentmods.dev/badge/rules/bayesimpact/bayes-platform/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.
<a href="https://agentmods.dev/rules/bayesimpact/bayes-platform/permission-matrix"><img src="https://agentmods.dev/badge/rules/bayesimpact/bayes-platform/permission-matrix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00369 |
| Opus 5.5 | $0.00000 | $0.00148 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
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.
What it actually says
Permission Matrix Sync
How to declare a permission, protect a route, and list what the caller can see: .claude/skills/rbac/SKILL.md and ADR 0019. This rule only keeps the matrix in sync with the catalog.
docs/rbac-permission-matrix.md mirrors the RBAC catalog defined in:
packages/api-contracts/src/rbac/permissions.ts— permission string constants and theGlobalPermissioncontract. Declare a permission string only here.apps/api/src/domains/rbac/rbac.constants.ts— role keys and which role receives which permission. Import the permission strings from@caseai-connect/api-contracts. Do not redeclare them.
Whenever you add, rename, or remove a role, a permission, or a role/permission grant in those files, you MUST update the corresponding table in docs/rbac-permission-matrix.md in the same change set.
Checklist:
- Every role in
ORGANIZATION_ROLE_PERMISSIONS/PROJECT_ROLE_PERMISSIONS/AGENT_ROLE_PERMISSIONS/REVIEW_CAMPAIGN_ROLE_PERMISSIONShas a column in the doc - Every granted permission has a row, checkmarks match the constants exactly
-
GlobalPermissionunion members all appear in the "Global roles" table - The project rows of the review campaign table match
PROJECT_PERMISSIONS_FROM_REVIEW_CAMPAIGNandREVIEW_CAMPAIGN_STATUSES_GIVING_PROJECT_PERMISSIONS
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 · +1 lines c53d6cf0d3ff
- 1mo ago Changed · +2 lines 8befa59bc1a8
- 1mo ago Changed 9206873fd662
- 1mo ago First seen · 21 lines · 0 tokens per session scan A 15c490d9e4f4
permission-matrix is a cursor rule published in the GitHub repository bayesimpact/bayes-platform (23 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 369 tokens. 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.
permission-matrix compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| permission-matrixbayesimpact/bayes-platform | Cursor rule | 23 | yesterday | MIT | A | 0 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 185k | 8d ago | MIT | A | 604 | Cursor |
| angular-20angular/angular | Cursor rule | 101k | yesterday | MIT | A | 0 | Cursor |
| dev-standardapache/superset | Cursor rule | 75k | yesterday | Apache-2.0 | A | 1,147 | Cursor |
| prefer-assertions-over-defensive-checksprisma/orm | Cursor rule | 48k | yesterday | Apache-2.0 | A | 0 | Cursor |
| prefer-direct-imports-over-module-mocksprisma/orm | Cursor rule | 48k | yesterday | Apache-2.0 | A | 0 | Cursor |
| shared-plane-packagesprisma/orm | Cursor rule | 48k | yesterday | Apache-2.0 | A | 0 | Cursor |