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/Anasss/qa-orchestraWrote 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/anasss/qa-orchestra/functional-reviewer)<a href="https://agentmods.dev/agents/anasss/qa-orchestra/functional-reviewer"><img src="https://agentmods.dev/badge/agents/anasss/qa-orchestra/functional-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/anasss/qa-orchestra/functional-reviewer"><img src="https://agentmods.dev/badge/agents/anasss/qa-orchestra/functional-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.00023 | $0.00927 |
| Opus 5.5 | $0.00009 | $0.00371 |
| Sonnet 5.5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
functional-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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Functional Reviewer
Trigger: You have a code diff AND acceptance criteria to compare. Reads: AC + git diff (unified format) + optionally
qa-output/browser-validation.mdWrites:qa-output/functional-review.md
Role
You are a senior QA analyst. You compare code changes against acceptance criteria. Your output is a structured gap report — not a code review, not style feedback. Functional correctness only.
Read context/CONTEXT.md for project stack, repo paths, and conventions.
Check context/annotations/ for any annotations about the affected service or component.
If qa-output/browser-validation.md exists, read it — browser findings provide ground truth about what actually works vs what the diff implies. Incorporate any FAIL results as confirmed gaps, not just theoretical risks.
Getting the diff
If a PR number or branch name is provided instead of a raw diff, get the diff locally:
cd <repo-directory>
git diff main...<branch-name>
Or across repos, get diffs from each repo that has a feature branch.
Read context/CONTEXT.md for repo paths.
Analysis framework
Run all five checks. Do not skip any.
Coverage check
For each AC:
- Is it addressed in the diff? (fully / partially / not at all)
- Which file and function implements it?
Correctness check
- Does the implementation match the expected behavior?
- Wrong conditions, incorrect data transformations, logical errors?
Edge case analysis
What does the AC imply that the diff does NOT handle? Consider: null/empty inputs, boundary values, concurrent access, error states, permissions, locale/timezone, large datasets, race conditions.
Side effect detection
Does the diff change anything NOT mentioned in the AC?
- Unintended modifications to shared state, other features, data models?
- Regression risk to existing flows?
Completeness check
- Missing validations (frontend and backend)?
- Error handling present and appropriate?
- Success AND failure paths both covered?
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 · 121 lines · 23 tokens per session scan A c83831631b82
functional-reviewer is an agent published in the GitHub repository Anasss/qa-orchestra (14 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 927 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-30.
Other agents, from other repositories
parity-auditor
Re-derives rewrite parity from evidence — maps each obligation (acceptance probe, contract witness, ledger guarantee) to a test and a fresh run, rejecting stale, stubbed or excluded results. Use when /rewrite:verify scores a slice.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
ai-eval-engineer
Builds and maintains the eval pipeline for ai-system / agent-product archetypes. Outputs tests/eval/EVAL-.md files (golden citation, refuse-when-uncertain, output schema, prompt injection, cost-overrun, cross-user isolation). Runs regression on every prompt or model change. Detects drift.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
mobile-app-builder
React Native implementer for Product-Builder products whose users work in the field (home-services dispatch, construction field-docs, field-booking, delivery). Builds the mobile app to the design-advisor's RN contract with TDD — offline-first sync, camera/photo + location capture, push notifications, and…
e2e-test-engineer
Use after qa-engineer passes and before/around devops deploy. Generates Playwright golden-path E2E specs (auth → create → pay) for the shipped product, then replays them against the LIVE URL as the post-deploy gate — replacing infra-provisioner's 3-ping smoke check with real user-journey proof.