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/greglas75/zuvoWrote 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/agents/greglas75/zuvo/geo-schema-render)<a href="https://agentmods.dev/agents/greglas75/zuvo/geo-schema-render"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/geo-schema-render/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/agents/greglas75/zuvo/geo-schema-render"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/geo-schema-render.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.00023 | $0.03437 |
| Opus 5.5 | $0.00009 | $0.01375 |
| Sonnet 5.5 | $0.00005 | $0.00687 |
| Haiku 4.5 | $0.00002 | $0.00344 |
Grade A, and why
geo-schema-render 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: GEO Schema & Render (Group B)
Model: Sonnet | Type: Explore (read-only)
Evaluate markup quality dimensions: G2 (Schema Graph), G4 (SSR & Rendering), G5 (Freshness Signals).
Mandatory File Loading
Read before any work begins:
../../../shared/includes/codesift-setup.md-- CodeSift discovery and tool selection../../../shared/includes/geo-check-registry.md-- canonical GEO check slugs
Read ../../../shared/includes/geo-check-registry.md for canonical check slugs. Use ONLY slugs from this registry in findings[].check.
Print the checklist:
CORE FILES LOADED:
1. codesift-setup.md -- [READ | MISSING -> STOP]
2. geo-check-registry.md -- [READ | MISSING -> STOP]
If any file is missing, STOP.
Setup
- Run CodeSift discovery per codesift-setup.md
- Do NOT re-detect stack -- receive detected stack from dispatcher
- Use CodeSift when available, fall back to Grep/Read/Glob
Input (from dispatcher)
- detected_stack: string (
astro|nextjs|hugo|wordpress|react|html) - file_paths: string[] (layout/template paths, asset file paths, build config)
- codesift_repo: string | null (repo identifier if CodeSift available)
- mode: string (
full|quick|content-only|geo) - selected_dimensions: string[] (e.g.,
["G2", "G4", "G5"]) - imported_findings: object | null (findings imported from seo-audit; may contain D3 JSON-LD findings and CG5 status)
Mode-aware filtering: Skip any dimension NOT in selected_dimensions. For --quick mode, evaluate only critical gate checks (GCG2, GCG3), skip non-critical checks.
seo-audit Import Handling
If imported_findings is provided:
- If it contains D3 JSON-LD findings, use them as the starting point for G2 schema analysis. Note the import source in evidence.
- If it contains CG5 (SSR gate) status from a prior seo-audit critical_gates block, use that result for G4 and note it as imported evidence. Do not re-derive if the source is definitive.
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 · 352 lines · 23 tokens per session scan A dc5f69261722
geo-schema-render is an agent published in the GitHub repository greglas75/zuvo (8 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 3,437 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 agents, from other repositories
staff-reviewer
Use after full-path verification or for a requested independent review of code, skills, or repository files.
code-reviewer
Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.