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.
npx skills add williamzujkowski/standards --skill authorizationgit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/skills/williamzujkowski/standards/authorization)<a href="https://agentmods.dev/skills/williamzujkowski/standards/authorization"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/authorization/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/skills/williamzujkowski/standards/authorization"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/authorization.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.00049 | $0.03783 |
| Opus 5.5 | $0.00020 | $0.01513 |
| Sonnet 5.5 | $0.00010 | $0.00757 |
| Haiku 4.5 | $0.00005 | $0.00378 |
Grade A, and why
authorization-security 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authorization Security
Quick Navigation: Level 1: Quick Start (5 min) → Level 2: Implementation (30 min) → Level 3: Mastery (Extended)
Level 1: Quick Start (<800 tokens, 5 minutes)
Core Principles
- Least Privilege: Grant minimum permissions required (NIST AC-6)
- Separation of Duties: No single user controls entire critical process
- Defense in Depth: Multiple authorization checks at different layers
- Fail Secure: Default deny, explicit allow
- Audit Everything: Log all authorization decisions (AU-2)
RBAC vs ABAC Comparison
| Aspect | RBAC (Role-Based) | ABAC (Attribute-Based) |
|---|---|---|
| Model | Roles → Permissions | Attributes → Policies |
| Flexibility | Low (fixed roles) | High (dynamic rules) |
| Complexity | Simple to implement | Complex policy engine |
| Use Case | Traditional enterprise | Context-aware access |
| Example | admin, user, guest |
dept=finance AND time=business_hours |
| NIST Control | AC-3 (Access Enforcement) | AC-3, AC-4, AC-16 |
Essential Checklist
- Least privilege: Users have minimum required permissions (AC-6)
- Separation of duties: Critical operations require multiple approvals (AC-5)
- Role hierarchies: Roles inherit permissions logically
- Policy enforcement: Authorization checked at API gateway + service level
- OAuth2 scopes: Fine-grained permissions in access tokens
- Resource ownership: Users can only access their own resources
- Deny by default: Unknown requests rejected automatically
- Audit logging: All authorization decisions logged with user/resource/action
- Time-based access: Support for temporary permissions
- Policy testing: Unit tests for all authorization rules
Quick Example
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 524 lines · 49 tokens per session scan A 0056f300c1d8
authorization-security is a skill published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 3,783 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-29.
Other skills, from other repositories
backend-authorization
Use this skill when the user says 'authorization', 'access control', 'RBAC', 'ABAC', 'ReBAC', 'permissions', 'role', 'policy', 'Casbin', 'Cerbos', 'permission delegation', 'temporary access', 'break glass', 'super admin', 'JIT elevation', 'role hierarchy', or when designing or implementing authorization for any…
frontmcp-authorities
Use when implementing authorization and access control for FrontMCP tools, resources, prompts, or skills, deciding who may invoke what. Covers the RBAC, ABAC, and ReBAC models and when to choose each; JWT claims mapping per identity provider (Auth0, Keycloak, Okta, Cognito, Frontegg); reusable named authority…
configuring-oauth2-authorization-flow
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token.
auth-patterns
Use when implementing authentication (JWT, sessions, OAuth), authorization (RBAC, ABAC), password hashing, MFA, or security best practices for backend services.
Authorization Testing Patterns
Role-based and attribute-based access control testing including permission matrices, privilege escalation prevention, and resource-level authorization.
configuring-oauth2-authorization-flow
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0…