Borrowing it
Nothing to install: this file belongs to kint4/autoframe. 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/kint4/autoframe/main/.claude/skills/refactor/SKILL.mdgit clone --depth 1 https://github.com/kint4/autoframeWrote 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/kint4/autoframe/refactor)<a href="https://agentmods.dev/skills/kint4/autoframe/refactor"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/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/kint4/autoframe/refactor"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/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.00037 | $0.00466 |
| Opus 5.5 | $0.00015 | $0.00186 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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.
What it actually says
/refactor — Refactor to Autoframe Conventions
Type: Maintenance Description: Takes existing, messy Playwright tests and restructures them to follow Autoframe conventions — extracting Page Objects, applying AAA, grouping tests, and replacing brittle selectors.
Input Format
- A path to an existing spec or test file (or a pasted snippet)
- Optionally, a target feature name
Output Format
The refactored file(s) following Autoframe conventions, plus a short changelog of what was changed and why. May produce a new Page Object and/or fixture as part of the refactor.
Step-by-Step Instructions
- Read the target file and any related Page Objects/fixtures.
- Read the POM, spec, and fixture conventions in CLAUDE.md.
- Diagnose convention violations:
- Raw locators /
page.$()/ CSS selectors in tests → extract into a Page Object using semantic locators. - Inline locators in Page Object methods → move to the constructor.
- Missing AAA structure → add Arrange / Act / Assert.
- Ungrouped tests → wrap in Happy Path / Negative / Edge
describeblocks. - Technical test names → rewrite in plain language.
- Raw
pagewhere a fixture exists → switch to the custom fixture.
- Raw locators /
- Apply the refactor incrementally, preserving the original test intent and assertions.
- Extract a Page Object and fixture if the logic belongs there.
- Save files to their correct locations per the folder structure.
- Output a changelog: what moved, what was renamed, what was replaced.
Rules
- Preserve test behavior — never silently drop assertions.
- Preserving scope may leave Negative/Edge
describegroups empty — do not invent coverage the original didn't have. Instead, note the gap in the changelog and hand off to/new-specto fill it. - Never introduce
waitForTimeoutor CSS selectors during a refactor. - Place all new files in their conventional locations.
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 · 46 lines · 37 tokens per session scan A 0ea8ef2b63a9
refactor is a skill published in the GitHub repository kint4/autoframe (8 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 466 once invoked, about $0.0001 per session on Opus 5.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
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
aif-web-testing
Test web apps with Playwright, Vitest and k6: E2E, unit, integration, load, security, visual and a11y.
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.