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/jaktestowac/awesome-copilot-for-testers/test-code-reviewergit 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.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.1 | $0.00070 | $0.02862 |
| Opus 5 | $0.00035 | $0.01431 |
| Sonnet 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 5d 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.
- 5d 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 (113 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 2,862 once invoked, about $0.0003 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
prd-assistant
Product Requirements Document generator for your project. Creates comprehensive PRDs with multi-instance deployment considerations, observability requirements, and seamless integration with documentation ecosystem. Serves both technical teams and AI agent consumption. Cloud-agnostic with automatic provider detection.
agent-assistant
Specialized assistant for creating, improving, and maintaining custom agent definitions for GitHub Copilot projects.
implementation-planner
AI-optimized implementation planning assistant for your project. Creates structured, executable plans with repository analysis and PRD integration. Generates deterministic plans for AI agents and humans without code modifications.
feature-documenter
Feature design assistant for your project. Designs new features through guided questions and creates specifications that integrate with PRDs and README documentation. Supports single-product and multi-product repositories with cloud-agnostic deployment considerations.
critical-thinker
Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.