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 skills/rakovi4/continue-framework/test-reviewnpx skills add rakovi4/continue-framework --skill test-reviewgit 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/skills/rakovi4/continue-framework/test-review)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/test-review"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/test-review.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.00028 | $0.00667 |
| Opus 5 | $0.00014 | $0.00333 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
test-review 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 today.
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 - Improve Test Assertions
Usage
/test-review— review all tests/test-review {TestTarget}— review one test target
Available Templates
| Template | Purpose |
|---|---|
.claude/templates/testing/test-review-patterns.md |
Universal rules, anti-pattern catalog, assertion rules |
.claude/tech/{backend}/templates/testing/test-review-usecase.md |
Usecase test patterns (Statements purity, 3-tier DSL) |
.claude/tech/{backend}/templates/testing/test-review-rest.md |
REST controller test patterns (mock matching) |
.claude/tech/{backend}/templates/testing/test-review-storage.md |
Persistence test patterns |
.claude/tech/{backend}/templates/testing/test-review-acceptance.md |
Acceptance test patterns (HTTP response assertions) |
.claude/tech/{backend}/templates/testing/test-review-other.md |
Selenium, email, scheduling, security patterns |
Workflow
Scatter–gather: parallel read-only detectors find violations, then a single serial fixer applies them. The detectors never edit — only the fixer writes, one file at a time — so there are no concurrent writes to shared Statements files.
- Determine the test's layer (usecase / rest / storage / acceptance / selenium) — this selects the tech file each detector loads and whether the selenium detector runs.
- Dispatch the detectors concurrently and await all of them — start every
named agent before awaiting results, then gather every result. No dispatch is
detached or fire-and-forget: step 3 requires the complete result set.
Each runs only its cluster of
.claude/templates/workflow/test-review-checklist.mdand returns a findings table:test-review-assertions-agent— cluster A (assertion strictness)test-review-placement-agent— cluster P (test-class vs Statements placement)test-review-statements-agent— cluster S (Statements internal quality)test-review-selenium-agent— cluster Se — only for selenium/frontend tests; skip for pure backend tests.
- Gather + fix: hand all findings to
.claude/agents/test-review-agent.md(the serial fixer). It merges, dedups, applies fixes one file at a time, and prints the filledtest-review-output-format.md. It runs/test-runnerunless Stage 2 production work is concurrent; in that case the coordinator runs the joined test and implementation.
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.
- today Changed · +1 lines · -18 tokens per session 74f30214330a
- 4d ago First seen · 54 lines · 46 tokens per session scan A 89717c67061b
test-review is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 667 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…