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/validate-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/validate-schema)<a href="https://agentmods.dev/commands/authzed/authzed-marketplace/validate-schema"><img src="https://agentmods.dev/badge/commands/authzed/authzed-marketplace/validate-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.00017 | $0.00522 |
| Opus 5 | $0.00009 | $0.00261 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
validate-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 3d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate SpiceDB Schema
Validate any SpiceDB .zed schema file using the schema-validator agent. Works on
any .zed file -- plugin-generated, manually edited, or migrated from another system.
Process
Step 1: Locate Schema
If the user provided a schema file path, use that. Otherwise:
- Search for
*.zedfiles in the current working directory - If exactly one is found, use it
- If multiple are found, ask the user which to validate using AskUserQuestion
- If none are found, ask the user for the schema file location
Step 2: Launch schema-validator Agent
Use the Task tool to launch the schema-validator agent:
Task(
subagent_type="spicedb-dev:schema-validator",
description="Validate SpiceDB schema",
prompt="Validate the schema file at [path] and suggest improvements"
)
The agent will:
- Check syntax for
.zedschema language validity - Validate best practices (naming conventions, relation/permission structure)
- Suggest optimizations
- Identify potential issues (anti-patterns, missing type annotations, etc.)
Step 3: Present Results
Present the validation results to the user with:
- Summary: Pass/fail and number of issues found
- Issues: List each issue with its severity (error, warning, suggestion) and location
- Next steps:
- If issues found: describe what to fix and how
- If no issues: suggest running
/spicedb-dev:generate-schema(if no schema yet) or/spicedb-dev:implement-spicedb-checksto add authorization code
Tips
- This command works on any
.zedfile, not just plugin-generated schemas - Run after manually editing a schema to catch regressions
- Run after migrating a schema from another system to verify correctness
- The
generate-schemacommand runs this automatically after generation
Notes
- The
schema-validatoragent performs static analysis only -- it does not connect to a live SpiceDB instance - For runtime validation with actual relationships, use
spicedb serve-testing(seeauthorization-testingskill)
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.
- 3d ago First seen · 66 lines · 17 tokens per session scan A f20b9e0245dc
validate-schema is a command published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 17 tokens to every session and 522 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.