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-reviewgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWhat 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.00015 | $0.03691 |
| Opus 5 | $0.00008 | $0.01845 |
| Sonnet 5 | $0.00003 | $0.00738 |
| Haiku 4.5 | $0.00002 | $0.00369 |
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 2d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Review
Scope: always Cites:
- testability-patterns
- result-verification
- test-automation-maturity
- adversarial-review-protocol
- oracle-provenance
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status: pass=no issues, warn=minor, fail=critical Severity: error=compromises test effectiveness, warning=should fix, suggestion=improvement Confidence: high=mechanical fix (add missing await, stub clock, extract constant); medium=test redesign direction clear but assertion strategy may differ; none=requires human judgment (test scope, behavior specification)
Context needs: full-file
Knowledge Files
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/testability-patterns.md before analysis. Whole-file load: the agent uses the decision flow, the anti-patterns table, and all four patterns as one connected reference when flagging untestable code (missing interfaces, static factories, concrete class coupling). Never recommend a test workaround (reflection, InternalsVisibleTo, mocking concrete classes).
For maintainability findings (duplicated selectors/literals, UI-based setup), consult ${CLAUDE_PLUGIN_ROOT}/knowledge/test-automation-maturity.md. Whole-file load: apply its single-point-of-change check and graduated-disclosure thresholds (don't recommend abstraction below the count threshold).
For assertion-quality findings, consult ${CLAUDE_PLUGIN_ROOT}/knowledge/result-verification.md. Whole-file load: apply all verification patterns (state vs behavior, assertion patterns, rules) when classifying assertion-quality issues.
For oracle-provenance classification (SPEC-DERIVED / INDEPENDENT / CIRCULAR), consult ${CLAUDE_PLUGIN_ROOT}/knowledge/oracle-provenance.md. Whole-file load: apply the taxonomy, detection heuristics, and circular-ratio quality-cap rule to every file reviewed. Report the oracle-provenance ratio in the finding summary when any circular oracles are present. Whole-file load: name the specific verification pattern (Expected Object, Custom Assertion, Guard Assertion, Delta Assertion) that fixes a weak/cluttered/misleading assertion, and enforce one logical condition per test.
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.
- 2d ago First seen · 218 lines · 15 tokens per session scan A bc4042320a3a
test-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 3,691 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.