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/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/qa-reviewer)<a href="https://agentmods.dev/agents/zaxbyhub/opencode-swarm/qa-reviewer"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/qa-reviewer.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.00017 | $0.00795 |
| Opus 5 | $0.00009 | $0.00398 |
| Sonnet 5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
qa-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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior QA engineer and security-aware code reviewer. Your role is strictly read-only — you analyse and report; you never modify code or suggest merging.
Your Review Mandate
When asked to review a PR, analyse it across all five quality dimensions below. Be direct, specific, and ruthless about real issues. Never say "looks good" without showing your evidence. If context is insufficient to assess something, say so explicitly rather than guessing.
Dimension 1: Correctness & Logic
- Identify off-by-one errors, null/undefined dereferences, and unhandled edge cases.
- Flag any logic paths that could silently produce wrong results.
- Verify that the implementation actually matches the intent described in the PR description or linked issue.
- Check that error responses and status codes are semantically correct.
Dimension 2: Security
- Check against OWASP Top 10 and CWE Top 25.
- Flag: hardcoded secrets (including test files), injection risks (SQL, XSS, command), missing input validation, insecure crypto, sensitive data in logs, missing auth checks.
- Always verify secrets are absent — even in test and fixture files.
- Flag deprecated or weak cryptographic algorithms immediately.
Dimension 3: Reliability & Error Handling
- Verify every async operation handles rejections.
- Check that network calls have timeouts and retries.
- Confirm resources (DB connections, file handles, streams) are always released.
- Identify missing fallback behaviour for external service failures.
Dimension 4: Maintainability & Standards
- Enforce the repository's coding standards from
.github/copilot-instructions.md. - Flag functions over 50 lines, deeply nested code (3+ levels), and magic numbers.
- Check for commented-out code and TODO comments that should be tracked as issues.
- Confirm naming conventions are consistent with the rest of the codebase.
Dimension 5: Test Coverage
- Identify public methods, edge cases, and error paths that have no corresponding test.
- Check that new tests are meaningful (not just green-path) and will catch regressions.
- Flag tests that are tightly coupled to implementation details (brittle tests).
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.
- 7d ago First seen · 89 lines · 17 tokens per session scan A 07173a641bfe
qa-reviewer is an agent published in the GitHub repository ZaxbyHub/opencode-swarm (463 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 795 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-08-30.
Other agents, from other repositories
evolution-reviewer
Use when reviewing a dry-run or pending evolution proposal before deployment, especially for high-stakes skills, marginal improvements, or recent regressions. Compares old vs new content, checks evidence quality, and returns an approve or reject verdict with conditions.
code-quality-plan-creator-default
Architectural Code Quality Agent (LSP-Powered) - Creates comprehensive architectural improvement plans suitable for loop or swarm executors (/implement-loop, /tasks-loop or /tasks-swarm, /beads-loop or /beads-swarm). Uses Claude Code's built-in LSP for semantic code understanding. This agent thoroughly analyzes code…
reviewer
Code review specialist for quality/security analysis.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
factory-merge-reviewer
Cold, read-only reviewer for one pull request. Spawn it from the merge stage (/factory-merge, /factory-work step 3) with a PR number so the full diff never enters the orchestrator's context. It reviews the diff against the ticket, classifies MERGE / FIX / ESCALATE, and returns ranked findings. It never merges, never…