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 spicedb-schema-designgit 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/spicedb-schema-design)<a href="https://agentmods.dev/skills/authzed/authzed-marketplace/spicedb-schema-design"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/spicedb-schema-design/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/spicedb-schema-design"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/spicedb-schema-design.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.00046 | $0.01771 |
| Opus 5 | $0.00023 | $0.00886 |
| Sonnet 5 | $0.00009 | $0.00354 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
SpiceDB Schema Design 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 9d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpiceDB Schema Design
This skill guides the design of effective SpiceDB schemas for authorization systems. Use this when modeling permissions, relationships, and access control for applications.
Overview
SpiceDB uses a schema language to define:
- Resources (objects to protect, like documents or organizations)
- Relations (connections between resources and subjects, like ownership or membership)
- Permissions (computed access rights based on relations, like view or edit)
Good schema design requires understanding the application's domain, identifying resources and their relationships, and modeling permissions that reflect business requirements.
Quick Reference
| Need to... | Read This |
|---|---|
| Find a pattern for your use case | references/patterns.md |
| Check if a design is an anti-pattern | references/anti-patterns.md |
| See a working GitHub-style schema | examples/github-style.zed or examples/github.yaml |
| See a Google Docs-style schema | examples/google-docs-style.zed or examples/docs-style-sharing.yaml |
| See a multi-tenant SaaS schema | examples/multi-tenant-saas.zed |
| See a minimal two-role ReBAC schema | examples/basic-rebac.yaml |
| See caveats / ABAC (IP allowlist, rate limits) | examples/caveats.yaml |
| See SaaS feature entitlements / plan gating | examples/entitlements.yaml |
| See platform-level superuser / admin bypass | examples/superuser.yaml |
| See user-defined roles (like JIRA project roles) | examples/user-defined-roles.yaml |
| See Google IAM-style role hierarchy | examples/google-iam.yaml |
| See AI agents delegated access on behalf of a user | examples/ai-agents.yaml |
| See a schema split across multiple validation files | examples/multiple-validation-files/ |
| Evolve an existing schema safely | references/schema-evolution.md |
When to Use This Skill
Use this skill when:
- Starting a new SpiceDB implementation
- Modeling permissions for a feature or module
- Refactoring an existing authorization system
- User asks about relation vs permission design choices
- Clarifying how to represent hierarchies or role-based access
What ships with it
19 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.
- examples/ai-agents.yaml 2.6 KB
- examples/basic-rebac.yaml 1.6 KB
- examples/caveats.yaml 2.6 KB
- examples/docs-style-sharing.yaml 4.4 KB
- examples/entitlements.yaml 2.2 KB
- examples/github-style.zed 2.8 KB
- examples/github.yaml 5.7 KB
- examples/google-docs-style.zed 3.2 KB
- examples/google-iam.yaml 23 KB
- examples/multi-tenant-saas.zed 4.7 KB
- examples/multiple-validation-files/README.md 1.8 KB
- examples/multiple-validation-files/schema.zed 15 KB
- examples/multiple-validation-files/validations/admin-role.yaml 3.5 KB
- examples/multiple-validation-files/validations/reader-role.yaml 1.7 KB
- examples/superuser.yaml 2.2 KB
- examples/user-defined-roles.yaml 9.5 KB
- references/anti-patterns.md 15 KB
- references/patterns.md 15 KB
- references/schema-evolution.md 3.3 KB
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.
- 9d ago First seen · 160 lines · 46 tokens per session scan A a7a19649b63a
SpiceDB Schema Design is a skill published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,771 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…