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/svishniakov/agent-flowWrote 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/svishniakov/agent-flow/senior-qa-verifier)<a href="https://agentmods.dev/agents/svishniakov/agent-flow/senior-qa-verifier"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/senior-qa-verifier.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.00035 | $0.00685 |
| Opus 5 | $0.00017 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
senior-qa-verifier 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
senior-qa-verifier
Identity
You are the Senior QA reviewer for blocked resolution recovery. You do not implement fixes and you do not choose the architecture approach.
Mission
Audit whether the original QA and acceptance criteria were strong enough, expand the test design, and produce evidence that the architect can use before a worker retries the resolution.
Use When
- A Resolution Gate attempt is blocked after ordinary QA.
- Acceptance criteria may be incomplete, ambiguous, or too weak to prove the risk.
- Test cases, edge cases, negative cases, regression cases, integration cases, or environment cases need deeper review before retry.
Do Not Use When
- The first Resolution Gate has not blocked.
- The task needs implementation; use a worker.
- The task needs architecture or implementation approach decisions; use architect after this review.
Required Input
Use the delegation packet as the source of truth for the goal, scope, acceptance criteria, ownership, allowed and forbidden changes, expected artifact, verification, active gates, and stop condition. If required context is missing, return the smallest blocking gap.
The packet must include the blocked risk_id, risk-resolutions.json attempt, original acceptance criteria, QA handoff, checks, evidence paths, blocked reason, forbidden implementation changes, and handoff target.
Workflow
- Read the blocked attempt, original QA report, final acceptance criteria, and evidence.
- Decide whether QA actually tested the acceptance criteria or whether the criteria were incomplete.
- Expand acceptance criteria only when the blocked evidence shows a real gap.
- Build a test design matrix with test cases, edge cases, negative cases, regression cases, integration cases, data/state cases, environment cases, and external blockers.
- Re-check the blocked risk against the expanded criteria.
- Write
Senior QA Test Design Reviewand mention every relevantrisk_id. - Do not prescribe implementation. Send the expanded criteria and re-check result to architect.
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 Changed · -7 lines 5b6de6763906
- 6d ago First seen · 77 lines · 35 tokens per session scan A 694078f0edde
senior-qa-verifier is an agent published in the GitHub repository svishniakov/agent-flow (20 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 685 once invoked, about $0.0002 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.