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 laurigates/claude-plugins --skill code-refactorgit clone --depth 1 https://github.com/laurigates/claude-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/laurigates/claude-plugins/code-refactor)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/code-refactor"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/code-refactor/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/laurigates/claude-plugins/code-refactor"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/code-refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.00784 |
| Opus 5.5 | $0.00016 | $0.00314 |
| Sonnet 5.5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
code-refactor 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 16d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use This Skill
| Use this skill when... | Use something else when... |
|---|---|
| A file or directory has mixed side effects and business logic | Deduplicating code across files → /code:dry-consolidation |
| Functions mutate state or parameters | Detecting code smells without fixing → /code:antipatterns |
| Business logic is tangled with I/O or logging | Reviewing overall quality and architecture → /code:review |
| Imperative loops can be replaced with map/filter/reduce | Large multi-phase refactor spanning 10+ files → /workflow:checkpoint-refactor |
| Deep nesting obscures intent |
Context
- Target path: !
echo "$1"
Parameters
$1: Required file path or directory to refactor
Your task
Delegate this task to the agents-plugin:refactor agent.
Use the Agent tool with subagent_type: agents-plugin:refactor to refactor the specified code. Pass all the context gathered in Context to the agent.
The refactor agent should:
-
Identify refactoring opportunities — look for these FP code smells:
- Side effects (mutation, I/O, logging) mixed into computation functions
- Parameters or external state mutated in place
- Imperative loops (
for,while) that could bemap,filter,reduce, orflatMap - Shared mutable state accessed across functions
- Deep nesting where early returns or guard clauses would clarify intent
- Business logic entangled with I/O at call sites
- Duplicated transformation logic
-
Apply functional programming principles:
- Pure functions: Extract computation into functions with no side effects — same input always produces same output
- Immutability: Replace in-place mutation with data transformations (
spread,map,Object.assign, structural copies) - Composition: Build complex behavior from small, focused, single-purpose functions
- Higher-order functions: Replace imperative loops with
map,filter,reduce,flatMap,find - Explicit effects: Push I/O, logging, and mutations to the outermost boundary; keep inner functions pure
- Early returns / guard clauses: Validate preconditions at the top, return early to avoid deep nesting
- DRY / KISS: Eliminate repetition; prefer the simplest shape that works
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.
- 16d ago Changed b5c6c52c7bce
- 1mo ago First seen · 79 lines · 39 tokens per session scan A 6cc66a768a8a
code-refactor is a skill published in the GitHub repository laurigates/claude-plugins (59 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 784 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-09-03.
Other skills, from other repositories
review-feedback
Address code review/PR comments: verify each, then fix.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
audit-comment-residue
Read-only classifier that flags residue in code comments: history narration, plan or session references, conversational asides, ticket or PR back-references, origin notes, and workarounds with no link or removal condition. Use when asked to 'audit code comments' or report which comments only make sense with the chat…
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.
pr-analyzing
Use this skill when the user asks to analyze a specific GitHub pull request, review a PR's architectural impact, assess what changed in a PR and why it matters, or research the code relationships affected by a PR — example triggers like "analyze PR.