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 irahardianto/awesome-agv --skill refactoring-patternsgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/refactoring-patterns)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/refactoring-patterns"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/refactoring-patterns/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/irahardianto/awesome-agv/refactoring-patterns"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/refactoring-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 90 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 91 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00026 | $0.00733 |
| Opus 5.5 | $0.00010 | $0.00293 |
| Sonnet 5.5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
refactoring-patterns 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- refactoring-patterns — 98% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Patterns
Catalog of safe, incremental code transformation patterns.
When to Invoke
- Executing
/refactorcommand - Technical debt remediation
- Pattern migration (e.g., callbacks → async/await)
- Code smell resolution from static analysis findings
Code Smell Taxonomy
Structural Smells
| Smell | Detection | Refactoring |
|---|---|---|
| Long method | >30 lines | Extract method |
| Large class | >300 lines or >5 responsibilities | Extract class |
| Long parameter list | >4 parameters | Introduce parameter object |
| Feature envy | Method uses another class's data more than its own | Move method |
| Data clumps | Same fields appear together repeatedly | Extract class |
| Primitive obsession | Primitives where domain types belong | Introduce value object |
Coupling Smells
| Smell | Detection | Refactoring |
|---|---|---|
| God class | One class knows/does too much | Extract classes by responsibility |
| Circular dependency | A → B → A | Introduce interface, dependency inversion |
| Inappropriate intimacy | Classes access each other's internals | Move method, extract interface |
| Shotgun surgery | One change requires touching many files | Move related code together |
Safe Transformation Techniques
1. Characterization Tests
Before refactoring, write tests that capture current behavior:
Run existing code → record outputs → assert in tests → now refactor safely
2. Strangler Fig Pattern
Gradually replace old implementation with new:
Old Code ← requests
↓ gradually route to
New Code ← requests (eventually all traffic)
Old Code ← delete
3. Branch by Abstraction
- Create abstraction (interface) over existing implementation
- Modify all clients to use abstraction
- Create new implementation behind abstraction
- Switch to new implementation
- Remove old implementation
4. Parallel Run
Run old and new implementations simultaneously, compare outputs:
Request → Old Implementation → Response (returned to user)
→ New Implementation → Response (logged, compared)
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 · 93 lines · 26 tokens per session scan A fdeed15d8113
refactoring-patterns is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 733 once invoked, about $0.0001 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-system-design
Review a system design someone else provided - screenshot, drawio, Mermaid, slides, doc, or IaC - by extracting it into a confirmed fact sheet, then scoring it on the nine axes.
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
review-ticket
Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.
common-feedback-reporter
Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.
code-review
Run an AI-assisted PR code review using multi-layer lenses with confidence scoring.
common-code-review
Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.