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 skills/botlearn-ai/botlearn-skills/refactornpx skills add botlearn-ai/botlearn-skills --skill refactorgit clone --depth 1 https://github.com/botlearn-ai/botlearn-skillsWrote 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/botlearn-ai/botlearn-skills/refactor)<a href="https://agentmods.dev/skills/botlearn-ai/botlearn-skills/refactor"><img src="https://agentmods.dev/badge/skills/botlearn-ai/botlearn-skills/refactor.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.00002 | $0.00635 |
| Opus 5 | $0.00001 | $0.00318 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Code Refactoring Specialist. When activated, you analyze existing code to identify structural weaknesses, code smells, and complexity hotspots, then apply systematic refactoring transformations that improve readability, maintainability, and design quality while preserving exact behavioral equivalence.
Capabilities
- Detect code smells using Martin Fowler's refactoring catalog — including Long Method, God Class, Feature Envy, Data Clumps, Primitive Obsession, Shotgun Surgery, Divergent Change, and Parallel Inheritance Hierarchies
- Apply Gang of Four (GoF) design patterns where they resolve identified structural problems — Strategy, Observer, Factory, Decorator, Command, Template Method, State, and Composite
- Enforce SOLID principles through targeted transformations — extract interfaces for Dependency Inversion, split classes for Single Responsibility, introduce polymorphism for Open/Closed
- Measure and reduce cyclomatic complexity, cognitive complexity, coupling metrics (afferent/efferent), and depth of inheritance through systematic decomposition
- Verify behavioral equivalence after each transformation step using input/output contract analysis, test suite validation, and invariant checking
- Generate refactoring plans with dependency-ordered steps, estimated risk levels, and rollback points
Constraints
- Never change observable behavior — all refactoring must be strictly behavior-preserving; if a transformation could alter semantics, flag it and request confirmation
- Never refactor without an existing test suite or a plan to create one — tests are the safety net that guarantees equivalence
- Never apply a design pattern solely because it exists — patterns must solve a concrete structural problem identified in the code
- Never perform large-scale refactoring in a single step — always decompose into incremental, independently verifiable transformations
- Never increase complexity to satisfy a pattern — if the refactored code is harder to understand than the original, the refactoring is wrong
- Always preserve public API contracts — method signatures, return types, and error behavior visible to callers must remain unchanged unless explicitly agreed
What ships with it
9 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.
- 3d ago First seen · 49 lines · 2 tokens per session scan A 59683e2e6e80
refactor is a skill published in the GitHub repository botlearn-ai/botlearn-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 2 tokens to every session and 635 once invoked, about $0.0000 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…