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/commands/authzed/authzed-marketplace/migrate)<a href="https://agentmods.dev/commands/authzed/authzed-marketplace/migrate"><img src="https://agentmods.dev/badge/commands/authzed/authzed-marketplace/migrate/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/commands/authzed/authzed-marketplace/migrate"><img src="https://agentmods.dev/badge/commands/authzed/authzed-marketplace/migrate.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.00029 | $0.14295 |
| Opus 5.5 | $0.00012 | $0.05718 |
| Sonnet 5.5 | $0.00006 | $0.02859 |
| Haiku 4.5 | $0.00003 | $0.01430 |
Grade A, and why
migrate 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 — 786 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate to SpiceDB
Phase 0 of the migration pipeline, and the migration's front door: analyze the source system, hold the single pre-flight gate, write the plan every later phase reads, and route into phase 1.
This command decides nothing on its own and converts nothing. It launches the
migration-analyzer agent, presents everything that agent found, resolves it with the
user in one batch, and records the result. Batching is the point: the decisions interact
-- tenancy constrains the identifier strategy, which constrains the data rewrite, which
constrains every call site -- and a user asked one question at a time cannot see those
interactions.
Outputs, written to [output-dir] (default: [project-dir] -- the project being migrated, not the shell's current working directory, which would scatter this pipeline's state into an unrelated place and leave every later phase unable to find it):
migration-map.json-- the machine-readable record of every decision, the identifier map, and phase status, in the shapemigrating-to-spicedb/references/findings-report.mdspecifies. Every later phase reads and writes state here, and nowhere else.migration-plan.md-- a human-readable rendering of that same file, for review. No phase parses it back in.
The plan is a pure rendering of the map, regenerated every time a phase touches it -- see
migrating-to-spicedb/references/findings-report.md's "Two groups of sections, one rule
each" for exactly which sections that covers.
Exactly one gate runs per migration. This command is it. /spicedb-dev:migrate-schema
holds a reduced inline gate only when it is run standalone with no map present; once
this command has written migration-map.json, that inline gate is skipped by its own step 1
and phase 1 reads the recorded state instead of re-asking.
Progress Tracking
Before starting, use TaskCreate to create a task for each step. Use TaskUpdate to mark each
task in_progress when starting and completed when done.
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 · 786 lines · 29 tokens per session scan A 5af57482283f
migrate is a command published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 14,295 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-08-31.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…