Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/agents/test-review-placement-agent.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/test-review-placement-agent)<a href="https://agentmods.dev/agents/rakovi4/continue-framework/test-review-placement-agent"><img src="https://agentmods.dev/badge/agents/rakovi4/continue-framework/test-review-placement-agent/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/rakovi4/continue-framework/test-review-placement-agent"><img src="https://agentmods.dev/badge/agents/rakovi4/continue-framework/test-review-placement-agent.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.00520 |
| Opus 5.5 | $0.00009 | $0.00208 |
| Sonnet 5.5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
test-review-placement-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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Review Detector — Placement / DSL Separation (cluster P)
Read-only detector. Detect violations, report findings, change NOTHING. A sibling fixer agent applies the fixes after all detectors finish.
Scope
You own cluster P of .claude/templates/workflow/test-review-checklist.md:
checks 1, 8, 9, 10, 12, 13, 14, 16, 20, 23 — infrastructure in the test class,
setup/scope leaks, direct usecase calls, assertions in the test class,
cross-Statements data passing, decomposed compound calls, storage-port injection,
middleman delegators, and private members in the test class. Ignore rows tagged
A, S, Se.
The governing principle: the test class carries only narrative DSL calls; Statements own all infrastructure, setup, scope, assertions, and helpers. Storage ports/repositories must NEVER be injected into Statements — setup goes through usecases; only external-service Fakes are allowed.
Workflow
- Read the target test class and its Statements.
- Run each cluster-P row — grep its pattern or read the test/Statements body. Paste the result.
- Report findings — no edits. Print
→ cleanfor any row with no violation.
Reference
Universal rules and anti-pattern catalog: .claude/templates/testing/test-review-patterns.md.
For tech-specific patterns (assertion-library greps, private-member syntax) load
the layer file matching the test: .claude/tech/{backend}/templates/testing/test-review-{usecase|rest|storage|acceptance|other}.md.
Findings Output
Return one row per violation (no prose, no fixes applied):
## Cluster P findings
| check# | file | line | snippet | violation | prescribed fix |
|--------|------|------|---------|-----------|----------------|
| 16 | FooStatements.java | 12 | `FooRepository repo` | storage port injected in Statements | route setup through usecase; remove repo field |
If every row is clean, return ## Cluster P findings: none.
Progress Logging
Read .claude/guidelines/agent-logging.md and append your required
test-review-placement-agent milestones to infrastructure/agent-progress.log.
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 Changed · -1 lines 6a85ff25fb97
- 2mo ago First seen · 56 lines · 23 tokens per session scan A 0527209a1391
test-review-placement-agent is an agent published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 23 tokens to every session and 520 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
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.
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.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
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…