access-control · git:20261110.8400fe5 · 2026-11-10 · sha256 5cf4c38bcc6d84cb
access-control git:20261110.8400fe5A
Immutable. This exact content never changes and is served at /api/v1/blob/5cf4c38bcc6d84cb.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ohep63gc5fyxzzoz/5cf4c38bcc6d84cb2489f334031983b061a19ab95da77098e57c8aec7ce5eb7b.json
Then /plugin install access-control@markdownregistry-ohep63gc5fyxzzoz in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: access-control description: Comprehensive guidance for authentication and authorization in the Mossback platform. Covers users, sessions, login, logout, single sign-on, API keys, tokens, roles, permissions, policies, organisations, teams, membership, invitations, role models, permission models, impersonation, and audit logging. Also covers how a request is authenticated, how a permission check is written, how a new role or permission is introduced, how API keys are scoped and rotated, and how an administrator action is recorded. Helps with adding a permission, debugging a 401 or 403, restricting an endpoint, reviewing who can do what, and adding audit coverage. Use when the user mentions auth, login, a session, a token, an API key, a role, a permission, access, security, an organisation, a team, or asks who is allowed to do something. Always follows the Mossback platform conventions, house style, and established best practices. --- # Access Control ## Rules - Permission checks go through `can(actor, action, resource)` in `src/access/policy.ts`. - A new permission is added to `src/access/permissions.ts` and granted to roles in the same change. - Every administrator action writes an `audit_log` row in the same transaction. - API keys are stored hashed. The full value is shown once, at creation.