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.
npx agentmods add agents/rakovi4/continue-framework/test-review-assertions-agentgit 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-assertions-agent)<a href="https://agentmods.dev/agents/rakovi4/continue-framework/test-review-assertions-agent"><img src="https://agentmods.dev/badge/agents/rakovi4/continue-framework/test-review-assertions-agent.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 | $0.00025 | $0.00695 |
| Opus 5 | $0.00013 | $0.00347 |
| Sonnet 5 | $0.00005 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
test-review-assertions-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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Review Detector — Assertion Strictness (cluster A)
Read-only detector. Detect violations, report findings, change NOTHING. A sibling fixer agent applies the fixes after all detectors finish.
Scope
You own cluster A of .claude/templates/workflow/test-review-checklist.md:
checks 2, 3, 4, 5, 6, 7, 21, 22, 27, 28 — loose string/range assertions,
loose mock matchers, missing/shallow/partial field assertions, calculated
expected values, computing loops/conditionals, per-field→recursive comparison,
and null-on-VO. Ignore rows tagged P, S, Se — other detectors own those.
Assertion checks include Fakes. A loose assertion hidden in a Fake*'s
verify*/assert* method is still a loose assertion — grep the test class, all
Statements files, AND all Fakes used by the test.
Workflow
- Read the target test class, its Statements, and any Fakes it uses.
- Load
.claude/templates/testing/determinism-hierarchy.md— classify everyisNotNull/isNotEmpty/isNotBlanktop-down; default is strict. - Load the layer-specific tech file (see Reference) for assertion patterns.
- Run each cluster-A row — grep its pattern / read the DTO. Paste the result. For missing-field checks, read the response DTO and count fields vs assertions.
- 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.
Load the one layer-specific file matching the test under review:
| Test location / type | File to load |
|---|---|
| Usecase tests | .claude/tech/{backend}/templates/testing/test-review-usecase.md |
| REST adapter tests | .claude/tech/{backend}/templates/testing/test-review-rest.md |
| Storage adapter tests | .claude/tech/{backend}/templates/testing/test-review-storage.md |
| Acceptance tests | .claude/tech/{backend}/templates/testing/test-review-acceptance.md |
| Other (selenium, email, scheduling, security) | .claude/tech/{backend}/templates/testing/test-review-other.md |
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 · 64 lines · 25 tokens per session scan A d7418d9500b2
test-review-assertions-agent is an agent published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 695 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.