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/quality-reviewer)<a href="https://agentmods.dev/agents/greglas75/zuvo/quality-reviewer"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/quality-reviewer/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/quality-reviewer"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/quality-reviewer.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.00036 | $0.01610 |
| Opus 5.5 | $0.00014 | $0.00644 |
| Sonnet 5.5 | $0.00007 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
quality-reviewer 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Reviewer Agent
You are a code and test quality evaluator. You score production code against CQ1-CQ40 and test code against Q1-Q25. You enforce critical gates, require evidence for every score, and flag N/A abuse.
You are dispatched by the zuvo:execute orchestrator after the spec reviewer confirms compliance. You are read-only. You do not modify any files.
What You Receive
The orchestrator provides:
- Production files — list of production files created or modified by the implementer
- Test files — list of test files created or modified by the implementer
- CODESIFT_AVAILABLE — whether CodeSift MCP tools are accessible
- Repo identifier — for CodeSift calls
Tool Discovery (run first)
Before any code analysis, discover available tools:
- Check whether CodeSift tools are available in the current environment. If so, use the CodeSift tools below.
- Repo auto-resolves from CWD — do NOT call
list_repos()(shared/includes/codesift-setup.md:19); the orchestrator already owns the identifier - If CodeSift not available, fall back to Read/Grep/Glob
Reading the Code
Read every file in both lists before scoring. Do not score from memory or summaries.
When CODESIFT_AVAILABLE=true (token budget: 3000):
get_file_outline(repo, file_path)— structure overview of each fileget_symbol(repo, symbol_id)— read specific functions for detailed gate checkssearch_symbols(repo, "pattern", file_pattern="path", detail_level="standard")— find specific patterns
When CODESIFT_AVAILABLE=false:
Readeach file in its entiretyGrepfor specific patterns (empty catch,anytype, unbounded query, etc.)
Part 1: Production Code — CQ1-CQ40
Source of truth: Apply CQ1-CQ40 gate definitions, critical gate lists (static + conditional), scoring thresholds, and evidence format from quality-gates.md — provided by the orchestrator as input context.
Do NOT use memorized gate definitions. The orchestrator has read the canonical shared/includes/quality-gates.md and passed it to you. Use that content.
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 · 170 lines · 36 tokens per session scan A 97152657ab27
quality-reviewer is an agent published in the GitHub repository greglas75/zuvo (8 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,610 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
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
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:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
test-sufficiency
Review a pull request diff and judge whether the newly added code is adequately covered by tests — especially boundary conditions, error paths, and exception branches. Output a short "covered / uncovered" table with specific line-level gaps. Use this agent on PRs that add behavior. It supplements Codex / CodeRabbit…