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/samibs/skillfoundry/refactornpx skills add samibs/skillfoundry --skill refactorgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/refactor)<a href="https://agentmods.dev/skills/samibs/skillfoundry/refactor"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/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.00006 | $0.02891 |
| Opus 5 | $0.00003 | $0.01445 |
| Sonnet 5 | $0.00001 | $0.00578 |
| Haiku 4.5 | $0.00001 | $0.00289 |
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 yesterday.
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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Agent
You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.
Shared Modules: See agents/_tdd-protocol.md for TDD enforcement during refactoring.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
REFACTORING PHILOSOPHY
"Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior." - Martin Fowler
Core Principles:
- Behavior Preservation: Tests must pass before AND after refactoring
- Small Steps: Make incremental changes, verify after each step
- Test Coverage: Ensure comprehensive tests exist before refactoring
- No Feature Changes: Refactoring ≠ adding features
- Documentation: Update comments/docs to reflect new structure
PRE-REFACTORING VALIDATION
BEFORE starting any refactoring, verify:
1. Test Coverage Check
- [ ] Comprehensive test suite exists
- [ ] All tests pass (green baseline)
- [ ] Edge cases are covered
- [ ] Integration tests exist for critical paths
If tests are missing or failing:
⚠️ Cannot refactor without passing tests. Run
/testerfirst to establish test baseline.
2. Behavior Baseline
- [ ] Document current behavior (inputs/outputs)
- [ ] Identify all public APIs/interfaces
- [ ] List all dependencies
- [ ] Note any side effects
3. Refactoring Scope
- [ ] What specific code smells are being addressed?
- [ ] What improvements are expected?
- [ ] Are there any constraints (performance, compatibility)?
- [ ] Is this part of a larger refactoring effort?
REFACTORING PATTERNS
Common Code Smells to Address
| Smell | Refactoring Technique | Risk Level |
|---|---|---|
| Long Method | Extract Method | Low |
| Large Class | Extract Class | Medium |
| Duplicate Code | Extract Function/Class | Low |
| Long Parameter List | Introduce Parameter Object | Low |
| Data Clumps | Extract Class | Medium |
| Primitive Obsession | Replace Primitive with Object | Low |
| Switch Statements | Replace with Polymorphism | Medium |
| Feature Envy | Move Method | Low |
| Inappropriate Intimacy | Move Method/Extract Class | Medium |
| Comments | Extract Method (self-documenting code) | Low |
| Magic Numbers | Extract Constant | Low |
| Dead Code | Remove Dead Code | Low |
| Speculative Generality | Remove Unused Abstraction | Low |
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.
- yesterday First seen · 450 lines · 6 tokens per session scan A e9a7cad134a5
refactor is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 2,891 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-09-03.
Other skills, from other repositories
ring:running-dev-cycle
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
testing-strategy
Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD.
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…