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 agentmods add commands/authzed/authzed-marketplace/implement-spicedb-checksgit 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/implement-spicedb-checks)<a href="https://agentmods.dev/commands/authzed/authzed-marketplace/implement-spicedb-checks"><img src="https://agentmods.dev/badge/commands/authzed/authzed-marketplace/implement-spicedb-checks.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.05148 |
| Opus 5 | $0.00016 | $0.02574 |
| Sonnet 5 | $0.00006 | $0.01030 |
| Haiku 4.5 | $0.00003 | $0.00515 |
Grade A, and why
implement-spicedb-checks 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 4d 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 — 590 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement SpiceDB Permission Checks
Add SpiceDB client calls for permission checks and lookup operations to application code.
Step 0: Verify or Generate Client
Before adding operation calls, verify a SpiceDB client exists in the codebase (search for
authzed.NewClient, v1.NewClient, or equivalent). If not, generate client initialization
code using the connection management pattern from
skills/spicedb-best-practices/references/client-patterns.md. The client should be a
singleton initialized at application startup, not per-request. For production TLS, see
the same reference.
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.
Supported Operations
- CheckPermission -- single permission check at an authorization boundary
- BulkCheckPermission -- check multiple permissions in one call (for list filtering)
- LookupResources -- find all resources a subject can access with a given permission
- LookupSubjects -- find all subjects that have a given permission on a resource
Process
Step 1: Understand the Context
Ask the user using AskUserQuestion:
-
Operation type: Which check/lookup operation to implement?
- Single permission check (CheckPermission)
- Bulk permission check (BulkCheckPermission)
- List accessible resources (LookupResources)
- Find subjects with access (LookupSubjects)
-
Programming language: What language?
- Go
- TypeScript/JavaScript
- Python
-
Target location: Where to add the code?
- Specific file/function
- Let checkpoint-identifier agent analyze and suggest
- New file/module
Step 2: Locate Target Code
If user specified files, read them. Otherwise:
- Use Task tool to launch
checkpoint-identifieragent - Agent will analyze codebase and suggest where to add authorization
- Agent uses data flow analysis to find authorization boundaries
Step 3: Load Best Practices
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.
- 4d ago First seen · 590 lines · 32 tokens per session scan A e3854ae5e72c
implement-spicedb-checks is a command published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 32 tokens to every session and 5,148 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.