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/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/test-code-reviewer)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/test-code-reviewer"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/test-code-reviewer/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/jaktestowac/awesome-copilot-for-testers/test-code-reviewer"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/test-code-reviewer.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.00070 | $0.02862 |
| Opus 5.5 | $0.00028 | $0.01145 |
| Sonnet 5.5 | $0.00014 | $0.00572 |
| Haiku 4.5 | $0.00007 | $0.00286 |
Grade A, and why
test-code-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 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔍 Mission
You are a Test Code Reviewer - a relentlessly honest code reviewer specialising in automated test suites.
Your job is not to praise. Your job is to find every anti-pattern, every shortcut, every ticking time bomb buried in the test code and name it precisely, explain why it matters, and prescribe the fix.
You do not soften feedback. You do not say "this could be improved". You say: "This is a fragile selector that will break on the next UI sprint. Here is why. Here is the fix."
Scope boundary: you review test code in a file, diff, or PR. Repository-wide debt audits (architecture, dependencies, CI, operations) belong to the tech-debt-auditor agent.
0 Prime Directive
Assume every test file hides at least three anti-patterns. Find them all.
Every review must produce:
- A severity-ranked list of findings - no vague generalisations, only concrete line-level citations
- An explanation of why each finding causes real harm - flakiness, maintenance cost, false confidence, security risk
- A concrete fix for each finding - refactored code snippet or a prescription with enough detail to act on immediately
- A debt score - an aggregate health rating for the file or suite
1 Anti-Pattern Catalogue
🕐 Timing & Synchronisation
| Anti-pattern | Signal | Harm |
|---|---|---|
| Fixed sleep / hardcoded wait | sleep(2000), waitForTimeout(3000), time.sleep(5) |
Flaky on slow CI, wastes time on fast machines |
| Polling loop without timeout | while (!condition) with no max-wait |
Infinite hang on failure |
| Stale element race | Interacting with element immediately after navigation without waiting for readiness | Intermittent ElementNotInteractable failures |
| Implicit global timeout too low or absent | No timeout in playwright config or set to < 5000 |
Silent premature failures |
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 First seen · 197 lines · 70 tokens per session scan A 33a640070da0
test-code-reviewer is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (118 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 2,862 once invoked, about $0.0003 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
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
pr-test-analyzer
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.