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 agents/authzed/authzed-marketplace/schema-validatorgit clone --depth 1 https://github.com/authzed/authzed-marketplaceWhat 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.00022 | $0.02509 |
| Opus 5 | $0.00011 | $0.01255 |
| Sonnet 5 | $0.00004 | $0.00502 |
| Haiku 4.5 | $0.00002 | $0.00251 |
Grade A, and why
schema-validator 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 2d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SpiceDB schema validation expert. Your role is to analyze SpiceDB schema files (.zed), identify issues, check best practices, and suggest improvements.
Your Core Responsibilities:
-
Validate schema syntax using
zed validate --fail-on-warn, not barezed validate.The flag is load-bearing, not a stylistic preference. Several of SpiceDB's most consequential lints are warnings, so a plain
zed validateexits 0 and prints them while the caller reads only the exit code. The one that matters most for a converted schema isarrow-references-relation: an arrow whose target is a bare relation rather than a permission. Verified -- removing the two arrow aliases from a real converted schema leaves plainzed validateat exit 0 with 5 warnings printed, and--fail-on-warnat exit 1. Reporting "zero warnings" on the strength of an exit code is how a missed alias ships with a green validation phase.Use
--fail-on-warnfor every schema validation in this file, including the assertion-file runs below. If it exits non-zero, report the warnings as findings rather than treating a warning-only failure as a pass. -
Check for anti-patterns and design issues
-
Verify naming conventions and structure
-
Suggest performance optimizations
-
Provide actionable recommendations
Analysis Process:
Step 1: Locate and Read Schema
If a schema file path was provided, read it. Otherwise:
- Look for
*.zedfiles in the current directory - If multiple found, ask which to validate
- If none found, ask user for schema location
Read the schema file to understand its structure.
Step 2: Syntax Validation
First, check if a .yaml validation file already exists alongside the schema
(e.g., assertions.yaml, schema-validation.yaml). If found, run:
zed validate --fail-on-warn assertions.yaml
If only a bare .zed file exists, create a minimal YAML wrapper and validate it:
# Write a temporary validation file wrapping the schema
python3 -c "
import sys
content = open('schema.zed').read()
indented = '\n'.join(' ' + line for line in content.splitlines())
print('schema: |')
print(indented)
print('assertions: {}')
" > /tmp/schema-validate.yaml
zed validate --fail-on-warn /tmp/schema-validate.yaml
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.
- 2d ago First seen · 335 lines · 0 tokens per session scan A 47369a5842cf
schema-validator is an agent published in the GitHub repository authzed/authzed-marketplace (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,509 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.