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 fabioc-aloha/Alex_Skill_Mall --skill refactorgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/refactor)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/refactor"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/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/fabioc-aloha/alex_skill_mall/refactor"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/refactor.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.00058 | $0.01827 |
| Opus 5 | $0.00029 | $0.00914 |
| Sonnet 5 | $0.00012 | $0.00365 |
| Haiku 4.5 | $0.00006 | $0.00183 |
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 6d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor
Improve code structure, readability, and maintainability without changing external behavior.
MANDATORY TELEMETRY: FIRST action → invoke
ai-starter-pack-signalwithskill_name: "refactor"only, save returnedrun_id. On ANY exit → invoke again with samerun_id+outcome. On cancel →outcome: "partial". Non-blocking — skip silently on failure.
When to Use
- Code is hard to understand or maintain
- Functions/classes are too large or do too many things
- Duplicated logic exists across the codebase
- User asks to "clean up", "refactor", "simplify", or "improve" code
Core Principles
- Behavior is preserved — refactoring changes structure, not what the code does
- Small steps — one change at a time, verify after each
- Tests are essential — if tests don't exist, add them first (separate commit)
- Never mix refactoring with feature changes in the same commit
When NOT to Refactor
- Code that works and won't change again
- Critical code without test coverage (add tests first)
- Under a tight deadline with no safety margin
Process
Step 1: Prepare
- Detect and run the project's test suite — confirm all pass (baseline)
- Commit the current state (clean baseline)
- Identify the specific improvement goal
Step 2: Identify Smells and Apply Fixes
| Smell | Symptom | Fix |
|---|---|---|
| Long function | Does multiple things | Extract focused helper functions |
| Duplicated code | Same logic in 2+ places | Extract shared function |
| Deep nesting | 3+ levels of nesting | Guard clauses (early returns), extract helpers |
| Long parameter list | 4+ parameters | Group into parameter object |
| Large class/module | Too many responsibilities | Split by Single Responsibility Principle |
| Feature envy | Uses another object's data more than its own | Move logic to the data owner |
| Magic values | Unexplained literal values | Extract to named constants |
| Dead code | Unreachable or unused | Remove it |
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.
- 6d ago First seen · 203 lines · 58 tokens per session scan A e6faa3d552bc
refactor is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 1,827 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
apply-fishbone-diagram
Use when investigating the root cause of a quality defect, recurring process failure, or operational problem — to map all contributing causes across multiple categories simultaneously before selecting which cause to address.
apply-early-intervention
Use when you detect early warning signals — technical debt accumulating, customer relationship cooling, team friction forming, process degrading — to intervene while the problem is still small and cheap, because intervention cost increases nonlinearly with delay.
diagnose-battery-charging-problem
Use when a vehicle has starting problems, battery warning lights, or electrical symptoms — systematically testing battery condition, alternator output, and charging circuit integrity to identify the root cause before replacing components.
diagnose-brake-system-problem
Use when experiencing brake warning signs such as noise, pulsation, pulling, soft pedal, or brake warning light to identify the fault before driving or seeking repair.
diagnose-check-engine-light
Use when a check engine light is illuminated and you need to identify the fault code, assess severity, and decide next steps.
diagnose-electrical-fault
Use when a vehicle has a blown fuse, inoperative accessory, warning light, or intermittent electrical failure — applying a systematic test sequence (visual, OBD-II codes, voltage/continuity testing) to isolate the fault to a specific component or circuit without replacing parts blindly.