Borrowing it
Nothing to install: this file belongs to cacr92/WeReply. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cacr92/WeReply/main/.claude/skills/refactoring/SKILL.mdgit clone --depth 1 https://github.com/cacr92/WeReplyWrote 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/cacr92/wereply/refactoring)<a href="https://agentmods.dev/skills/cacr92/wereply/refactoring"><img src="https://agentmods.dev/badge/skills/cacr92/wereply/refactoring.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.1 | $0.00089 | $0.03996 |
| Opus 5 | $0.00044 | $0.01998 |
| Sonnet 5 | $0.00018 | $0.00799 |
| Haiku 4.5 | $0.00009 | $0.00400 |
Grade A, and why
refactoring 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 — 642 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Skill
Systematic code refactoring guidance for improving code quality, maintainability, and design without changing functionality.
Overview
This skill provides refactoring strategies for:
- Extracting methods/functions for better organization
- Removing code duplication (DRY principle)
- Simplifying complex logic and reducing cyclomatic complexity
- Improving naming and readability
- Applying design patterns appropriately
- Reducing technical debt while maintaining functionality
When This Skill Applies
This skill activates when:
- Code is difficult to understand or maintain
- Functions/methods are too long or complex
- Similar code appears in multiple places
- Naming is unclear or inconsistent
- Design patterns could improve structure
- Technical debt needs to be reduced
- Performance optimizations are needed
Refactoring Principles
Core Rules
- Preserve Functionality: Refactoring should NOT change behavior
- Small Steps: Make incremental changes with tests between each
- Test Coverage: Ensure tests pass before and after refactoring
- Commit Often: Save working state frequently
- Document Why: Explain reasons for significant changes
Red, Green, Refactor
# 1. Ensure tests pass (GREEN)
cargo test
npm test
# 2. Make small refactoring change
# 3. Run tests again (still GREEN)
cargo test
npm test
# 4. Commit if tests pass
git commit -m "refactor: extract material validation logic"
# Repeat
Common Code Smells & Refactorings
1. Long Method/Function
Smell:
// ❌ 200+ line function doing multiple things
pub async fn create_formula_with_materials(
&self,
dto: CreateFormulaDto,
) -> Result<Formula> {
// Validate name
if dto.name.is_empty() {
return Err(anyhow!("Name cannot be empty"));
}
if dto.name.len() > 100 {
return Err(anyhow!("Name too long"));
}
// ... 50 more validation lines
// Check duplicate name
let exists = sqlx::query_scalar!(
"SELECT COUNT(*) FROM formulas WHERE name = ?",
dto.name
)
.fetch_one(&self.pool)
.await?;
if exists > 0 {
return Err(anyhow!("Formula already exists"));
}
// Validate materials
for material in &dto.materials {
if material.proportion < 0.0 || material.proportion > 100.0 {
return Err(anyhow!("Invalid proportion"));
}
// ... 30 more validation lines
}
// Insert formula
// ... 100 more lines
}
What ships with it
1 file 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.
- 6d ago First seen · 642 lines · 89 tokens per session scan A fd4943e7e31f
refactoring is a skill published in the GitHub repository cacr92/WeReply (6 stars, last pushed 7mo ago), licensed MIT. It adds 89 tokens to every session and 3,996 once invoked, about $0.0004 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.