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 d-mariano/spicyclaude --skill refactor-modifiergit clone --depth 1 https://github.com/d-mariano/spicyclaudeWrote 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/d-mariano/spicyclaude/refactor-modifier)<a href="https://agentmods.dev/skills/d-mariano/spicyclaude/refactor-modifier"><img src="https://agentmods.dev/badge/skills/d-mariano/spicyclaude/refactor-modifier.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.00048 | $0.01513 |
| Opus 5 | $0.00024 | $0.00757 |
| Sonnet 5 | $0.00010 | $0.00303 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
refactor-modifier 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 8d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor / Rewrite Modifier
This is NOT a standalone workflow. It adds sections to the greenfield-design or feature-integration workflow when the task involves significant restructuring, replacement, or rewriting of existing code.
When to Apply
Apply if any of these are true:
- Replacing an existing component with a fundamentally different implementation
- Moving responsibilities between existing components
- Old and new code must coexist during a migration period
- The data model changes require backfilling or dual-writing
- Consolidating multiple existing patterns into a new one
- Existing tests need significant rewriting, not just updating
If you're just adding new code with minor cleanup, use feature-integration without this modifier.
Phase 1 Addition: Legacy Analysis
Add after the environment survey (greenfield) or codebase reconnaissance (integration).
Current State Assessment
- What exists today: Read the actual code of the component(s) being replaced. Describe real behavior, not surface summaries.
- Why it's being replaced: Specific problems — performance, maintainability, correctness, scalability. Be concrete with evidence from the code.
- What it gets right: What the current implementation handles well that must be preserved. This is critical — refactors that lose working behavior are bugs.
- Hidden responsibilities: Non-obvious things the current code does. Side effects, implicit ordering, undocumented behavior other components depend on. Read the callers, not just the implementation.
- Data state: Data accumulated under the current implementation. Shape, volume, quality. Known inconsistencies or tech debt in stored data.
Dependency Audit
- Who calls this code? Every caller/consumer with file paths. Use Grep.
- Who does this code call? Every downstream dependency.
- What tests exercise this code? Test files and quality assessment (behavior tests vs. implementation tests).
- What monitoring exists? Dashboards, alerts, SLOs tied to the current implementation.
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.
- 8d ago First seen · 138 lines · 48 tokens per session scan A 60365e0f2fbf
refactor-modifier is a skill published in the GitHub repository d-mariano/spicyclaude (5 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,513 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…