Borrowing it
Nothing to install: this file belongs to DynamoDS/DynamoHome. 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/DynamoDS/DynamoHome/master/.claude/skills/refactor/SKILL.mdgit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWrote 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/dynamods/dynamohome/refactor)<a href="https://agentmods.dev/skills/dynamods/dynamohome/refactor"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/refactor/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/dynamods/dynamohome/refactor"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/refactor.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.00000 | $0.00571 |
| Opus 5.5 | $0.00000 | $0.00228 |
| Sonnet 5.5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
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 2mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Workflow – DynamoHome
Use this workflow when restructuring code without changing its observable behavior.
Steps
1. Define scope and goal
Before touching code, identify:
- What is being refactored and why (readability, duplication, type safety, etc.)
- What the observable behavior is, so you can verify it is preserved afterward
- Which files are in scope — do not touch files outside the stated scope
2. Establish a baseline
Run the full test suite to confirm the starting state is green:
npm run lint:check
npm run test:unit
npm run build
If any of these fail before you start, stop and fix them first (or confirm with the user).
3. Refactor incrementally
- Make one logical change at a time (extract a component, rename a type, consolidate duplicate logic)
- Run
npm run test:unitafter each meaningful change to confirm nothing broke - Note each stable checkpoint — makes it easy to revert one step without losing all work
4. DynamoHome-specific risks
| Refactor | Risk to check |
|---|---|
| Renaming a prop or interface | Any callers using the old name? Grep src/ for it |
Moving a component to Common/ |
Update all import paths in consumers |
| Extracting a custom hook | Verify useSettings() context is still available if the hook needs it |
| Consolidating or renaming locale keys | Check all 14 locale files; grep src/ for old key usages |
Changing utility.ts function signatures |
Verify tests/__mocks__/chromeMock.ts covers the new signature |
Changing SettingsContext shape |
Grep for useSettings and verify every callsite still works |
| Renaming a global window callback | Never do this — Dynamo calls them by name from .NET |
5. Final verification
npm run lint:check # No new lint errors
npm run test:unit # All tests pass
npm run build # Dev bundle builds
npm run bundle # Production bundle builds (if webpack config was touched)
What NOT to do during a refactor
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.
- 2mo ago First seen · 63 lines · 0 tokens per session scan A 6f215b214f10
refactor is a skill published in the GitHub repository DynamoDS/DynamoHome (3 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 571 tokens. 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…