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 skills add bengous/claude-code-plugins --skill refactorlib-ccgit 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/skills/bengous/claude-code-plugins/refactorlib-cc)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/refactorlib-cc"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/refactorlib-cc/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/skills/bengous/claude-code-plugins/refactorlib-cc"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/refactorlib-cc.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.00052 | $0.01481 |
| Opus 5.5 | $0.00021 | $0.00592 |
| Sonnet 5.5 | $0.00010 | $0.00296 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
refactorlib-cc 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
refactorlib
Audit a codebase for handcrafted code that could be replaced by existing dependencies.
Projects accumulate utility code over time. Some predates a dependency that now covers the same ground; some was written before the team discovered a library API. Removing these duplications shrinks maintenance surface and leverages battle-tested implementations with better edge-case handling and security patches.
Project context
- deps: !
bun -e "const p=JSON.parse(await Bun.file('package.json').text()); console.log(JSON.stringify({...p.dependencies,...p.devDependencies}))" 2>/dev/null - runtime: !
bun --version 2>/dev/null || node --version 2>/dev/null - has_effect: !
bun -e "const p=JSON.parse(await Bun.file('package.json').text()); console.log(p.dependencies?.effect || p.devDependencies?.effect ? 'yes' : 'no')" 2>/dev/null - has_bun: !
bun -e "const p=JSON.parse(await Bun.file('package.json').text()); console.log(p.devDependencies?.['@types/bun'] ? 'yes' : 'no')" 2>/dev/null - src_dirs: !
ls src/ 2>/dev/null | head -20
Workflow
Phase 1 -- Route on context
The project context above was resolved at skill load time. Use it to decide which pattern catalogs each agent should read:
- If has_effect == "yes": include
references/patterns/effect-infra.mdin the infra agent's pattern list - Always: include
references/patterns/runtime-infra.mdfor infra agent,references/patterns/general-utility.mdandreferences/patterns/runtime-utility.mdfor utility agent
The subagents have effect-usage and bun skills preloaded — no need to load companion
skills in the orchestrator.
Phase 2 -- Parallel exploration
Spawn two custom subagents in parallel. Each receives a short task prompt with:
- Project dependencies (from
depsabove) - Source directories (from
src_dirsabove) - Pattern catalog file paths to read (from Phase 1 routing)
- Guardrails:
~/.claude/skills/refactorlib-cc/references/guardrails.md - Report format:
~/.claude/skills/refactorlib-cc/references/report-format.md - The user's request (or "Full audit -- no scope restriction")
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 157 lines · 52 tokens per session scan A e2a45796b291
refactorlib-cc is a skill published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,481 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 skills, from other repositories
verify-change
A change-checking skill that reviews code differences and checks whether related documentation, tests, and records were updated.
verify-module
A module-checking skill that scans a project’s folders, code, and documentation. It expects each module to include a README.md and DESIGN.md, which explain how the module is used and why it was designed that way.
verify-quality
A code-quality checker that measures complexity, size, naming, and common code smells. It reports problems such as duplicated code, unused code, and overly long functions.
planning
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. If create-tasks is not visible, load it via loadtool (search "create tasks"). Do NOT use for new one-off workflows, single-workflow…
criticism-self-criticism
A structured review method for examining completed work, criticism, and repeated mistakes. It focuses on specific evidence, causes, effects, and practical improvements.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.