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 pattern-detection-walkthroughsgit 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/pattern-detection-walkthroughs)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/pattern-detection-walkthroughs"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/pattern-detection-walkthroughs/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/mickeyyaya/refactoring-skills/pattern-detection-walkthroughs"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/pattern-detection-walkthroughs.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01942 |
| Opus 5 | $0.00028 | $0.00971 |
| Sonnet 5 | $0.00011 | $0.00388 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
pattern-detection-walkthroughs 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 9d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern Detection Walkthroughs
Diagnostic Flow
Each walkthrough follows four steps:
- Smell Detection (
detect-code-smells) - Anti-Pattern Check (
anti-patterns-catalog) - Refactoring Selection (refactor skills)
- Design Pattern (prevent recurrence)
Walkthrough 1: God Class → Extract Class + Facade
Smell: Large Class — 15+ methods across auth, profiles, email, billing.
// BEFORE: UserManager does everything
class UserManager {
private db: Database; private mailer: Mailer; private stripe: StripeClient;
login(email: string, password: string): Session { /* ... */ }
logout(sessionId: string): void { /* ... */ }
updateProfile(userId: string, data: ProfileData): User { /* ... */ }
sendWelcomeEmail(userId: string): void { /* ... */ }
createSubscription(userId: string, plan: string): Subscription { /* ... */ }
processRefund(userId: string, amount: number): void { /* ... */ }
// ... 8 more methods
}
Anti-Pattern: God Object — changes to billing break auth; every dev edits same file.
Refactoring: Extract Class per responsibility (refactor-moving-features).
// AFTER: focused services
class AuthService { login(...) { } logout(...) { } }
class ProfileService { updateProfile(...) { } deleteAccount(...) { } }
class NotificationService { sendWelcomeEmail(...) { } sendInvoice(...) { } }
class BillingService { createSubscription(...) { } processRefund(...) { } }
Pattern: Facade — single entry point for coordinated multi-service flows.
class UserFacade {
constructor(private auth: AuthService, private profile: ProfileService,
private notifications: NotificationService, private billing: BillingService) {}
async registerUser(email: string, password: string, plan: string): Promise<User> {
const session = await this.auth.login(email, password);
await this.billing.createSubscription(session.userId, plan);
await this.notifications.sendWelcomeEmail(session.userId);
return this.profile.updateProfile(session.userId, { email });
}
}
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.
- 9d ago First seen · 223 lines · 55 tokens per session scan A ea9e0b94286a
pattern-detection-walkthroughs is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,942 once invoked, about $0.0003 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…