Oso to SpiceDB

Oso to SpiceDB is a skill for Claude Code from authzed/authzed-marketplace. It costs 19 tokens per session (3,532 once invoked), scanned A, original, Apache-2.0.

A migration guide for moving an application from Oso Cloud, a hosted authorization service that checks Polar policies and stored facts, to SpiceDB.

In plain words
What is it for?
Use it to map Polar rules, export or manually extract authorization data, and identify migration findings for a SpiceDB conversion.
Why use it?
It explains which Oso Cloud policies and data need to change during the move. It does not cover the deprecated embedded Oso library.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the spicedb-dev plugin — 8 skills, 15 commands, 3 agents shipped together

Good fit Use it to map Polar rules, export or manually extract authorization data, and identify migration findings for a SpiceDB conversion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/authzed/authzed-marketplace/oso-to-spicedb
Install

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.

Any agent
npx skills add authzed/authzed-marketplace --skill oso-to-spicedb
Clone the repo
git clone --depth 1 https://github.com/authzed/authzed-marketplace

Made for: Claude Code.

Or install spicedb-dev, the plugin that ships this one along with the rest of its 8 skills, 15 commands, 3 agents.

Wrote 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.

agentmods badge for Oso to SpiceDB

README.md
[![agentmods](https://agentmods.dev/badge/skills/authzed/authzed-marketplace/oso-to-spicedb/github.svg)](https://agentmods.dev/skills/authzed/authzed-marketplace/oso-to-spicedb)
Your own site
<a href="https://agentmods.dev/skills/authzed/authzed-marketplace/oso-to-spicedb"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/oso-to-spicedb/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.

agentmods 80×15 button for Oso to SpiceDB

Your own site · 80×15
<a href="https://agentmods.dev/skills/authzed/authzed-marketplace/oso-to-spicedb"><img src="https://agentmods.dev/badge/skills/authzed/authzed-marketplace/oso-to-spicedb.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,532 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.03532
Opus 5.5 $0.00008 $0.01413
Sonnet 5.5 $0.00004 $0.00706
Haiku 4.5 $0.00002 $0.00353

Measured 1mo ago against content hash f3b1f46f1d6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Oso to SpiceDB 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.

spicedb-dev/skills/oso-to-spicedb/SKILL.md · 247 lines

How it starts

The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Oso to SpiceDB

The conversion pack for Oso Cloud. migrating-to-spicedb owns the pipeline, the gate protocol, and the report formats; this skill supplies the source-specific rules that pipeline reads, per migrating-to-spicedb/references/pack-contract.md's ten items.

Nothing here restates the framework. If you are looking for how phases sequence, what a Class A finding is, or what migration-map.json holds, that is the framework skill.

What this pack covers

Oso Cloud -- the hosted (or self-hosted) service: a Polar policy plus facts, queried over the Check API. This is the supported source.

The deprecated osohq/oso library is not covered. The open-source embedded library (Polar files loaded in-process, host-language classes registered with the runtime) is marked deprecated by its own repository. Its policies are Polar and much of the policy mapping below still applies, but its data lives in the application's own objects rather than as facts, so there is nothing to export and references/data-mapping.md does not apply. If a project is on the OSS library, say so at the gate and treat the data phase as a hand-written extraction rather than a conversion.

The shape of the problem, in one paragraph

Oso's declarative core -- actor/resource blocks with roles, permissions, relations, and shorthand implication rules -- is close enough to Zanzibar that it translates mechanically. A has_role(User{"alice"}, "steward", Lab{"genomics"}) fact is a relationship tuple, with the role string doing exactly the job a SpiceDB relation name does. What does not translate is everything Polar can express beyond that core: facts with values instead of objects, comparisons between two stored facts, rules with a variable in the role position, and the local-filtering API that returns SQL. The cost of an Oso migration is almost never the schema. It is attributes, list endpoints, and the data-sync obligations the conversion creates.

Detection (pack contract item 1)

Read the full file on GitHub · 247 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 247 lines · 0 tokens per session scan A f3b1f46f1d6d

Subscribe to this mod's changes

Oso to SpiceDB is a skill published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 3,532 once invoked, about $0.0001 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-19.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens