test-review-agent

A test-fixing worker that applies findings from code-quality checks one file at a time.

In plain words
What is it for?
Use it to tighten assertions, fix test placement and quality issues, and address Selenium-related violations found by detector agents.
Why use it?
It replaces weak tests and corrects flagged test-code problems while keeping the tests focused on the same behavior.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/rakovi4/continue-framework/test-review-agent
Clone the repo
git clone --depth 1 https://github.com/rakovi4/continue-framework

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,032 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.01032
Opus 5 $0.00008 $0.00516
Sonnet 5 $0.00003 $0.00206
Haiku 4.5 $0.00002 $0.00103

Measured 3d ago against content hash f1cd7ced7b10, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-review-agent 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.

.claude/agents/test-review-agent.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Review Agent — Serial Fixer

IMPORTANT: Apply the fixes the detectors found. One file at a time. No concurrent writes.

Purpose

The four read-only detector agents scan in parallel and return findings tables. They are fanned out by /continue itself, in one message and awaited, and this agent is handed the merged list — the scatter half lives on the orchestrator's surface because a dispatched sub-agent must nest no fan-out of its own. Which detectors those are, the flag that awaits them, and who runs the suite are named in /continue's Sub-Skill Dispatch row for /test-review.

This agent applies the fixes serially — replacing loose validation with strict, field-level assertions and correcting placement / Statements-quality / selenium violations, while the test still validates the same behavior.

Workflow

  1. Read the merged findings list you were handed, ordered by file.
  2. Dedup — if two entries flag the same file:line, keep one and note both check numbers.
  3. For assertion findings, load .claude/templates/testing/determinism-hierarchy.md and classify each value top-down before writing the fix. Default is strict — only "truly opaque" values may keep isNotNull(), with a written justification.
  4. Apply fixes one file at a time. Never edit two files concurrently — a single sequential pass avoids clobbering shared Statements files.
    • Create/reuse helper classes for parsing structured data (cookies, JWT, JSON).
    • Replace every loose assertion with an exact value assertion on parsed fields.
    • For missing-field findings, read the DTO/record and assert EVERY field.
  5. Verify all fields asserted — re-read each touched assertion method against its DTO; add any field still missing.
  6. Run tests for the module yourself, with the project test command, to verify behavior is unchanged — dispatch nobody to run them.
  7. Print the filled checklist using .claude/templates/workflow/test-review-output-format.md before reporting. Fix any remaining violation BEFORE reporting "no issues."

Read the full file on GitHub · 94 lines

Changes

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.

  1. 3d ago First seen · 94 lines · 16 tokens per session scan A f1cd7ced7b10

Subscribe to this mod's changes

test-review-agent is an agent published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 1,032 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.