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/refactor-opportunity-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/refactor-opportunity-review)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/refactor-opportunity-review"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/refactor-opportunity-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.01575 |
| Opus 5 | $0.00014 | $0.00788 |
| Sonnet 5 | $0.00006 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
refactor-opportunity-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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Opportunity Review
Scope: on-demand Cites:
- design-smells
- adversarial-review-protocol
Dispatched by name at /build's slice review checkpoint
(../skills/build/SKILL.md sub-step 6) — once
per slice, after its steps are green, which is the moment this agent's
charter names ("assesses refactoring opportunities after tests pass") — by
../skills/test-driven-development/SKILL.md
§ REFACTOR 3a, and on demand via --agent refactor-opportunity-review.
Never by /code-review's per-diff panel (#1976). Because those dispatches
name it directly, Scope: on-demand removes it from the resolver's roster
without removing it from the pipeline. A refactoring opportunity is a
property of code that is already green, evaluated while the author still
has the option to restructure; by the time a full review panel runs, the
same ground is covered by structure-review (SRP, DRY, coupling, and —
since #2093 folded complexity-review into it — nesting, cognitive load,
and async-pattern judgment), which is Scope: always and overlaps this
lens's findings on the same diffs. Running it in both places bought a
second opinion on those axes, not a new axis.
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status: pass=code is clean, warn=refactoring opportunities exist, fail=critical duplication or complexity Severity: error=semantic duplication (real DRY violation), warning=high-value refactor opportunity, suggestion=nice-to-have cleanup Confidence: high=mechanical (extract method, rename); medium=judgment call (is this duplication semantic or structural?); none=requires domain knowledge
Context needs: full-file
Knowledge Files
Before analysis, read ${CLAUDE_PLUGIN_ROOT}/knowledge/design-smells.md#reinvented-built-in-cheat-sheet
— the per-language built-in map and the "What NOT to flag" guards (version/idiom
drift) for the use-the-platform findings — plus the "Reinvented built-in / helper"
and "Open-coded idiom" rows in ${CLAUDE_PLUGIN_ROOT}/knowledge/design-smells.md#design-smells-pattern-mapping.
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 · 129 lines · 28 tokens per session scan A e25b0d4ffe63
refactor-opportunity-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,575 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.