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/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/plugins/authzed/authzed-marketplace/spicedb-dev)<a href="https://agentmods.dev/plugins/authzed/authzed-marketplace/spicedb-dev"><img src="https://agentmods.dev/badge/plugins/authzed/authzed-marketplace/spicedb-dev/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/plugins/authzed/authzed-marketplace/spicedb-dev"><img src="https://agentmods.dev/badge/plugins/authzed/authzed-marketplace/spicedb-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spicedb-dev 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.
What it actually says
{
"name": "spicedb-dev",
"version": "1.1.0",
"description": "Comprehensive SpiceDB development toolkit for designing permission models, generating schemas, implementing authorization, testing, and migrating from other authorization systems (OpenFGA, Okta FGA, Oso Cloud) to SpiceDB",
"author": {
"name": "AuthZed"
},
"homepage": "https://github.com/authzed/authzed-marketplace/tree/main/spicedb-dev",
"repository": "https://github.com/authzed/authzed-marketplace",
"license": "Apache-2.0",
"keywords": ["spicedb", "authorization", "permissions", "development", "authzed", "schema", "modeling", "migration", "openfga"]
}
What it installs
The manifest is a name and a version. 8 skills, 15 commands, 3 agents travel with it, and installing the plugin installs all of them — 714 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill OpenFGA to SpiceDB A 58 tokens
- Skill Oso to SpiceDB A 19 tokens
- Skill SpiceDB Schema Design A 46 tokens
- Skill Migrating to SpiceDB A 62 tokens
- Skill SpiceDB Client Integration A 57 tokens
- Skill SpiceDB Best Practices A 46 tokens
- Skill Authorization Testing A 41 tokens
- Skill Authorization Planner A 40 tokens
- Command migrate-verify A 33 tokens
- Command migrate A 29 tokens
- Command migrate-data A 16 tokens
- Command migrate-schema A 17 tokens
- Command migrate-tests A 18 tokens
- Command implement-spicedb-checks A 32 tokens
- Command test-permissions A 14 tokens
- Command implement-spicedb-relationships A 24 tokens
- Command plan A 34 tokens
- Command generate-schema A 14 tokens
- Command design-model A 12 tokens
- Command validate-schema A 17 tokens
- Command migrate-code A 27 tokens
- Command audit-coverage A 33 tokens
- Command implement-spicedb A 25 tokens
- Agent migration-analyzer A 0 tokens
- Agent schema-validator A 0 tokens
- Agent checkpoint-identifier A 0 tokens
What ships with it
1 file beside plugin.json 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 Changed 4004cff1ba60
- 1mo ago First seen · 13 lines scan A e0e9aa6dfcad
spicedb-dev is a plugin published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
app-builder
Development, customization, testing, and deployment skills for Adobe App Builder projects, including the Workfront UI-extension suite (skills/appbuilder-workfront).
load-tester
Load and stress testing for APIs and web services.
rabbitmqadmin
Skill for inspecting RabbitMQ instances using the rabbitmqadmin CLI (rabbitmqadmin-ng).
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.
jpm-payments-skills
Conversational agent skills that walk a merchant from J.P. Morgan Payments onboarding through a working API integration. Supports Checkout and Online Payments in the initial release. Generates language-specific OAuth modules (Node/TypeScript, Python, Java idiomatic; other languages via canonical algorithm).
auth
Auth skills for Claude Code — scaffold hand-rolled auth endpoints and audit auth code against security best practices.