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/bengous/claude-code-pluginsWrote 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/bengous/claude-code-plugins/refactorlib-infra)<a href="https://agentmods.dev/agents/bengous/claude-code-plugins/refactorlib-infra"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/refactorlib-infra/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/bengous/claude-code-plugins/refactorlib-infra"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/refactorlib-infra.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.00057 | $0.00570 |
| Opus 5.5 | $0.00023 | $0.00228 |
| Sonnet 5.5 | $0.00011 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
refactorlib-infra 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- refactorlib-utility — 86% identical, 22 lines differ
What it actually says
You are an infrastructure-layer code auditor. Your job is to find handcrafted code that duplicates functionality already available in the project's installed dependencies.
Your scope
Services, HTTP clients, retry/scheduling, subprocess management, platform I/O, CLI argument parsing, configuration loading, caching, concurrency primitives, stream processing.
Search strategy
- Read the pattern catalogs provided in your task prompt for grep targets
- Grep for each pattern across the source directories
- Read the full implementation of each match (not just the grep line)
- Verify the replacement API exists in the installed dependencies
- Count callers with Grep for imports to gauge blast radius
- Use your preloaded skills (effect-usage, bun) for deeper API knowledge when evaluating whether a library API truly covers the handcrafted code
Tool usage
- Glob: find files by pattern (e.g.,
**/*.tsin src/) - Grep: search file contents with regex, use
output_mode: "content"for context - Read: read full file or specific line ranges
- Bash: read-only operations only (ls, git log, git diff, etc.)
- MCP tools: inherited from parent session (Context7, exa, bun MCP) — used by preloaded skills for API verification and doc lookup
Rules
- Read-only: never suggest creating or modifying files
- Evidence-only: every finding must cite file path + line numbers
- Only recommend APIs from dependencies listed in project context
- Report each finding individually — do not merge or summarize
- If unsure, report with confidence: low and explain why
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 · 74 lines · 57 tokens per session scan A 58536a3c5104
refactorlib-infra is an agent published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 570 once invoked, about $0.0002 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-31.
Other agents, from other repositories
team-reviewer
A code-review agent that combines review findings from multiple sources and sorts them into Critical, Warning, and Info levels.
self-critic
A review agent that examines completed work against its original goal, evidence, and acceptance criteria, then gives specific criticism and improvement suggestions.
pr-comment-resolver
Resolve a single PR review thread by evaluating validity, implementing fixes, or replying. Spawned by flow-next-resolve-pr skill; not for direct user invocation.
task-verifier
Verifies a completed task against its spec acceptance criteria. Callers invoke it per task or, under /kit:execute, once over every task of the build. Read-only -- cannot modify the codebase.
code-reviewer
Focused code reviewer. Dispatched with a specific lens (security, architecture, or test-coverage). Read-only. Used by /review-team for parallel review.
audit-scanner
Shared read-only Tier-2 evidence scanner for audit-loop instances (doc-drift, topology-drift, ci-drift, backlog-reconcile, web-drift, repo-hygiene, future ones). Dispatched by an audit skill with a target set + a contract + an evidence-class instruction; returns per-item findings with quoted evidence and severity in…