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 authzed/authzed-marketplace --skill authorization-plannergit clone --depth 1 https://github.com/authzed/authzed-marketplaceWrote 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/authzed/authzed-marketplace/authorization-planner)<a href="https://agentmods.dev/skills/authzed/authzed-marketplace/authorization-planner"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/authorization-planner/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/authzed/authzed-marketplace/authorization-planner"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/authorization-planner.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.00040 | $0.00793 |
| Opus 5.5 | $0.00016 | $0.00317 |
| Sonnet 5.5 | $0.00008 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
Authorization Planner 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authorization Planner
This plugin adds a first pass at SpiceDB fine-grained authorization to an application being built or modified. The goal is getting authorization structurally correct -- right permissions, right places, right operations. It is not a production hardening or debugging tool.
Ideal Workflow
Once, early -- before or alongside data model design
Run /spicedb-dev:plan. This scopes the work, produces authorization-plan.md,
and writes an authorization snippet to CLAUDE.md so permissions are considered
automatically in every future session without needing to invoke any command. This is
the most important setup step.
Then /spicedb-dev:design-model -- scans for existing model files and extracts
entity names. Produces permission-model.md.
Then /spicedb-dev:generate-schema -- converts the model to schema.zed.
Schema-validator runs automatically.
Deploy the schema externally: zed schema write schema.zed.
Continuously, alongside every feature
Every feature needs both operations -- this is the most common implementation mistake:
-
Relationship writes (
/spicedb-dev:implement-spicedb-relationships) -- run when writing handlers that create resources, grant membership, or delete resources. SpiceDB returns NO_PERMISSION for everything until relationships are written. Writes must come before checks. -
Permission checks (
/spicedb-dev:implement-spicedb-checks) -- run when writing any handler that reads, modifies, or deletes a resource on behalf of a user. For list endpoints, use LookupResources -- not CheckPermission in a loop.
Use /spicedb-dev:implement-spicedb when unsure which is needed -- it
communicates the paired requirement and routes to the right command.
Periodically
/spicedb-dev:audit-coverage produces a coverage matrix: every permission in
the schema vs. whether a corresponding check exists in code. Routes each gap to the
correct implement command.
Once, when stable
/spicedb-dev:test-permissions generates test fixtures and integration tests
from the schema.
What ships with it
2 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.
- 1mo ago First seen · 85 lines · 40 tokens per session scan A 460082aed117
Authorization Planner is a skill published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 793 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…