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 mickeyyaya/refactoring-skills --skill refactor-composing-methodsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-skillsWrote 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/mickeyyaya/refactoring-skills/refactor-composing-methods)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/refactor-composing-methods"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/refactor-composing-methods.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.00042 | $0.02025 |
| Opus 5 | $0.00021 | $0.01012 |
| Sonnet 5 | $0.00008 | $0.00405 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
refactor-composing-methods 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor: Composing Methods
Overview
These 9 techniques break down complex methods into smaller, readable pieces and eliminate duplication. Most frequently used refactoring techniques and the first defense against Bloater smells.
When to Use
- Method exceeds ~20 lines
- Comments explaining sections (each should be its own method)
- Same code block in multiple places
- Complex expressions hard to understand at a glance
- Temporary variables accumulate and obscure logic
Quick Reference
| Technique | Problem | Solution |
|---|---|---|
| Extract Method | Code fragment that can be grouped | Move into a named method |
| Inline Method | Method body is as clear as its name | Replace calls with body |
| Extract Variable | Complex expression hard to understand | Assign to descriptive variable |
| Inline Temp | Temp assigned once from simple expression | Replace references with expression |
| Replace Temp with Query | Temp holds reusable expression result | Extract to method, replace temp with call |
| Split Temporary Variable | Temp assigned more than once (not loop var) | Separate variable per assignment |
| Remove Assignments to Parameters | Method assigns to its parameters | Use a local variable instead |
| Replace Method with Method Object | Tangled locals prevent extraction | Turn method into its own class |
| Substitute Algorithm | Algorithm replaceable with clearer one | Swap the body |
Techniques in Detail
1. Extract Method
The most important refactoring. When in doubt, extract.
Before:
function printOwing(invoice: Invoice): void {
let outstanding = 0;
// print banner
console.log("***********************");
console.log("*** Customer Owes ***");
console.log("***********************");
// calculate outstanding
for (const order of invoice.orders) {
outstanding += order.amount;
}
// print details
console.log(`name: ${invoice.customer}`);
console.log(`amount: ${outstanding}`);
}
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 · 291 lines · 42 tokens per session scan A 7597eddf6a26
refactor-composing-methods is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 2,025 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…