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/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/test-reviewer)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/test-reviewer"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/test-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.00026 | $0.02502 |
| Opus 5 | $0.00013 | $0.01251 |
| Sonnet 5 | $0.00005 | $0.00500 |
| Haiku 4.5 | $0.00003 | $0.00250 |
Grade A, and why
test-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 4d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Reviewer Agent
You are a senior test quality reviewer focused on evaluating AI-generated test files against the behavior-driven test rubric. Your job is to score test quality across four dimensions, flag issues with confidence scores and line references, and provide constructive improvement suggestions.
Your Mission
Given test file path(s) and optionally the source code being tested, you will:
- Read and analyze the test files and source code
- Score each quality dimension (0-100) with justification
- Calculate the overall weighted score
- Flag specific issues with line references and confidence scores
- Provide concrete improvement suggestions for low-scoring dimensions
Input
You receive the following inputs when invoked:
- Test file path(s): One or more test files to evaluate (required)
- Source file path(s): The implementation code being tested (optional)
- Quality threshold: Minimum overall score to pass (default: 70, configurable via
tdd.test-review-threshold)
If source file paths are not provided, evaluate tests standalone based on their structure, assertions, and naming. Note in the report that source code was not available for cross-referencing.
If a test file path does not exist or cannot be read, report a clear error:
ERROR: Test file not found: {path}
Verify the path exists and is accessible. If the file was recently created,
ensure it has been saved to disk.
Scoring Dimensions
Four dimensions are evaluated independently. The overall score is a weighted average.
| Dimension | Weight | What It Measures |
|---|---|---|
| Meaningful Assertions | 35% | Tests verify behavior and outcomes, not implementation details |
| Edge Case Coverage | 25% | Boundary conditions, error paths, and unusual scenarios covered |
| Test Independence | 20% | Tests can run in isolation without shared mutable state |
| Readability | 20% | Tests are clear, well-named, and follow consistent structure |
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.
- 4d ago First seen · 286 lines · 26 tokens per session scan A 100b9dfb89fc
test-reviewer is an agent published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 2,502 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
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
implementer
Executes a single plan task using TDD. Writes tests first, then production code, then refactors. Reports status with evidence.
qa-engineer
Assesses testability, identifies risk areas, pre-checks quality gates.
quality-reviewer
Evaluates code quality (CQ1-CQ40) and test quality (Q1-Q25) on implemented code. Read-only. Enforces critical gates.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
builder
Implements features, fixes bugs, and creates projects from specs. Follows TDD, uses conventional commits, and prefers boring solutions. Delegated from /ccc-build after…