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 agentmods add skills/oreum-ai/smartstack/refactornpx skills add oreum-ai/smartstack --skill refactorgit clone --depth 1 https://github.com/oreum-ai/smartstackWhat 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 | $0.00000 | $0.00371 |
| Opus 5 | $0.00000 | $0.00186 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 yesterday.
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.
What it actually says
Skill: Refactor
When to use
When code works but is hard to read, duplicated, or fragile — and you want to improve its structure without changing behavior. Not for features; for making existing code cleaner and safer to change.
The golden rule
Refactoring never changes behavior. If behavior should change, that's a feature/fix — do it separately, so each diff is either "same behavior, cleaner" or "new behavior," never both.
Procedure
- Protect first. Ensure the code is covered by tests. If it isn't and it's risky, use
test-writerto add coverage BEFORE refactoring — the tests prove you didn't change behavior. - One transformation at a time. Rename, extract a function, remove duplication, simplify a conditional — each as its own small step. Run tests/lint after each step.
- Keep the diff focused. Don't reformat unrelated lines; it hides the real change.
- Follow existing patterns. Move shared logic into the right home rather than copy-pasting.
- Don't break the public shape. Keep function signatures / API contracts stable unless the task allows changing them.
- Verify. All tests green; lint/build clean; behavior identical.
Good refactor targets
- Duplicate fetches that should share a cached value.
- Repeated validation/guard logic that could be one helper.
- Long functions mixing data, logic, and presentation.
- Dead code, unclear names, deep nesting.
Checklist
- Covered by tests before starting.
- Behavior unchanged (tests still green, same outputs).
- One transformation per step, verified each time.
- Follows repo patterns; diff focused; quality gate clean.
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.
- yesterday First seen · 32 lines · 0 tokens per session scan A 9d1719b4d97e
refactor is a skill published in the GitHub repository oreum-ai/smartstack (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 371 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…