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/bdfinst/agentic-dev-team/test-smell-reviewgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/test-smell-review)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/test-smell-review"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/test-smell-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.00020 | $0.03924 |
| Opus 5 | $0.00010 | $0.01962 |
| Sonnet 5 | $0.00004 | $0.00785 |
| Haiku 4.5 | $0.00002 | $0.00392 |
Grade A, and why
test-smell-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 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Smell Review
Scope: test-files Cites:
- test-smells
- test-automation-principles
- test-doubles
- value-patterns
- test-pyramid
- fixture-construction
- test-organization
- test-refactoring
- testability-patterns
- result-verification
- database-test-patterns
- component-test-patterns
- cd-test-architecture
- microservice-testing
- adversarial-review-protocol
Dispatched only when the changeset touches a test file (#1978). Every smell
this agent detects — assertion roulette, eager tests, mystery guests, test
doubles, pyramid placement — is a property of test code, so a diff that
changes no test file gives it nothing to read and it would self-report
{"status": "skip"}. test-files is resolved by
scripts/select_lenses.py against the single shared encoding of
../knowledge/test-file-indicators.md
(hooks/lib/test_file_classify.py), so this scope covers every family that
file names — including test_*.py, __tests__/, and the C#/Java
annotation indicators that a glob list could not express. Note the
deliberate contrast with test-review, which stays Scope: always: its
coverage-gap check must see production diffs that add code without a
matching test, which is precisely a diff this scope excludes.
Output JSON (extends the shared contract in ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md with smell and remedyFamily fields. Whole-file load: short, canonical schema):
{"status": "pass|warn|fail|skip", "issues": [{"severity": "error|warning|suggestion", "confidence": "high|medium|none", "file": "", "line": 0, "smell": "", "message": "", "remedyFamily": "fixture-construction|result-verification|test-organization|test-refactoring|null", "suggestedFix": ""}], "summary": ""}
Status: pass=no smells, warn=minor smells, fail=behavior/project smell that undermines trust in the suite Severity: error=smell that makes the suite untrustworthy or unmaintainable (flaky, buggy test, false confidence), warning=should fix (fragile, obscure, overspecified), suggestion=improvement Confidence: high=named smell with a mechanical fix (add assertion message, inline mystery guest, downgrade mock to stub); medium=smell is clear but the redesign has options (split strategy, layer choice); none=requires human judgment (intended test level, whether a behavior is worth testing)
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 · 176 lines · 20 tokens per session scan A e755eb05f517
test-smell-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 3,924 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.