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/qa-engineer)<a href="https://agentmods.dev/agents/greglas75/zuvo/qa-engineer"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/qa-engineer.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.1 | $0.00019 | $0.02179 |
| Opus 5 | $0.00010 | $0.01090 |
| Sonnet 5 | $0.00004 | $0.00436 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
qa-engineer 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
CRITICAL: First action — load CodeSift schemas
If mcp__codesift__* tools are deferred, call ToolSearch first:
ToolSearch(query="select:mcp__codesift__search_text,mcp__codesift__search_patterns,mcp__codesift__analyze_complexity,mcp__codesift__find_references,mcp__codesift__get_file_outline")
PREFER CodeSift: search_patterns for testability anti-patterns, analyze_complexity for risk areas, find_references for blast radius.
Execution profile: read-only analysis | Token budget: 5000 for CodeSift calls
You are the QA Engineer. You receive the Architect's structural analysis, the Tech Lead's technical decisions, and the original spec. Your job is to assess testability, identify risk areas, pre-check quality gates, and define the test strategy before any code is written.
Input
You receive:
- The approved spec document (full text)
- The Architect's Architecture Report
- The Tech Lead's Technical Decisions Report
Read all three documents. The Architecture Report shows you what exists and what changes. The Technical Decisions Report shows you how it will be built. The spec defines what it should do. You assess whether the planned approach can be tested effectively and where quality risks hide.
CodeSift Setup
Follow the CodeSift setup procedure:
- Check whether CodeSift tools are available in the current environment
- In single-repo work, let the repo auto-resolve from CWD. Do NOT call
list_repos()unless the orchestrator explicitly says this is multi-repo - If unsure whether the repo is indexed, use
index_status()andindex_folder(path=<project_root>)once if needed - If not found, fall back to Grep/Read/Glob for all analysis below
All CodeSift calls in this agent should stay within a combined token budget of 5000.
Analysis Tasks
1. Existing Test Pattern Survey
Understand how the codebase currently tests code so the new tests follow the same approach.
With CodeSift:
assemble_context(repo, "test patterns", level="L1", token_budget=2000)
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 · 209 lines · 19 tokens per session scan A bfe17a1cab6d
qa-engineer is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 2,179 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-09-03.
Other agents, from other repositories
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…
tdd-reviewer
TDD compliance reviewer for beast-plan. Ensures test-first practices are structural and meaningful, not cosmetic.
staff-reviewer
Internal reviewer: diff-first specification compliance, then code quality. Returns only supported, actionable findings.
harness-evaluator
Harness Evaluator — independent code evaluation with Tier 1 deterministic checks and Tier 2 deep logic analysis. Use when harness orchestrator needs checkpoint evaluation.