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 ArabelaTso/Skills-4-SE --skill code-refactoring-assistantgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/code-refactoring-assistant)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/code-refactoring-assistant"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-refactoring-assistant/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/arabelatso/skills-4-se/code-refactoring-assistant"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-refactoring-assistant.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.00081 | $0.05968 |
| Opus 5.5 | $0.00032 | $0.02387 |
| Sonnet 5.5 | $0.00016 | $0.01194 |
| Haiku 4.5 | $0.00008 | $0.00597 |
Grade A, and why
code-refactoring-assistant 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 — 979 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Refactoring Assistant
Systematically improve code structure and quality through targeted refactorings. Identifies opportunities, suggests improvements, and applies changes while preserving behavior.
Core Capabilities
1. Code Smell Detection
Identify refactoring opportunities:
- Long methods/functions - Functions doing too much
- Large classes - Classes with too many responsibilities
- Duplicate code - Repeated logic across codebase
- Long parameter lists - Functions with many parameters
- Primitive obsession - Using primitives instead of objects
- Feature envy - Methods using other classes more than their own
- Data clumps - Same group of data appearing together
- Switch statements - Complex conditionals that could be polymorphic
2. Structural Refactorings
Improve code organization:
- Extract Method - Pull out code into new function
- Extract Class - Split class responsibilities
- Inline Method/Variable - Remove unnecessary indirection
- Move Method/Field - Relocate to appropriate class
- Rename - Improve naming clarity
- Change Function Signature - Update parameters
- Introduce Parameter Object - Group parameters into object
- Replace Conditional with Polymorphism - Use inheritance/interfaces
3. Simplification Refactorings
Reduce complexity:
- Decompose Conditional - Simplify complex if/else
- Consolidate Conditional - Combine related conditions
- Remove Dead Code - Delete unused code
- Simplify Boolean Expression - Make logic clearer
- Replace Magic Number with Constant - Named constants
- Replace Nested Conditional with Guard Clauses - Early returns
- Replace Loop with Pipeline - Use functional operations
4. Generalization Refactorings
Improve abstraction:
- Extract Interface - Define contracts
- Extract Superclass - Pull up common behavior
- Replace Type Code with Class - Use objects not constants
- Replace Conditional with Strategy - Pluggable behavior
- Form Template Method - Define algorithm skeleton
- Replace Constructor with Factory - Flexible object creation
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 · 979 lines · 81 tokens per session scan A e03f470f4454
code-refactoring-assistant is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (259 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 5,968 once invoked, about $0.0003 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-30.
Other skills, from other repositories
skill-code-quality
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
teach
Teach the user a new skill or concept, within this workspace.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
skill-incident-management
Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.
skill-pr-review
Comprehensive code review for pull requests using parallel multi-agent analysis. Audits CLAUDE.md compliance, checks for bugs, analyzes git history, reviews comments, and filters by confidence score. Use when reviewing a GitHub PR, mentions "code review", "review this PR", or "/code-review".