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/generate-schemagit 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/generate-schema)<a href="https://agentmods.dev/commands/authzed/authzed-marketplace/generate-schema"><img src="https://agentmods.dev/badge/commands/authzed/authzed-marketplace/generate-schema.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.00014 | $0.02093 |
| Opus 5 | $0.00007 | $0.01046 |
| Sonnet 5 | $0.00003 | $0.00419 |
| Haiku 4.5 | $0.00001 | $0.00209 |
Grade A, and why
generate-schema 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate SpiceDB Schema
Convert a permission model document to a SpiceDB schema (.zed file). After generation, automatically trigger the schema-validator agent to check the schema.
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.
Process
Step 1: Locate Permission Model
If the user provided a model file path, use that. Otherwise:
- Look for
permission-model.mdin the current directory - If not found, ask user for the model file location
- If no model exists, suggest running
/spicedb-dev:design-modelfirst
Step 2: Parse Permission Model
Read the permission model document and extract:
- Resource definitions with their relations
- Permission definitions with their expressions
- Hierarchical relationships
- Any special patterns (caveats, wildcards, etc.)
Step 3: Select a Reference Example
Before writing the schema from scratch, identify the closest matching example in
skills/spicedb-schema-design/examples/ and use it as a starting point or cross-reference.
Pattern matching guide:
| Permission model contains... | Start from |
|---|---|
| Simple writer/reader or owner/viewer roles | basic-rebac.yaml |
| IP allowlists, rate limits, time-based access | caveats.yaml |
| Groups with parent/child hierarchies | docs-style-sharing.yaml |
| SaaS subscription plans gating features | entitlements.yaml |
| Orgs, teams, repos with multiple role levels | github.yaml or github-style.zed |
| Platform-level superuser or admin bypass | superuser.yaml |
| Users defining their own roles at runtime | user-defined-roles.yaml |
| Roles with scoped inheritance across resource hierarchy | google-iam.yaml |
| Multi-tenant SaaS with tenant isolation | multi-tenant-saas.zed |
| Google Docs-style sharing | google-docs-style.zed |
| AI agents acting on behalf of a user | ai-agents.yaml |
| Schema tested across multiple independent validation files | multiple-validation-files/ (directory, not a modeling pattern) |
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 · 303 lines · 14 tokens per session scan A 77b8d3b802a4
generate-schema is a command published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,093 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
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.