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/kint4/autoframe/refactornpx skills add kint4/autoframe --skill refactorgit clone --depth 1 https://github.com/kint4/autoframeWhat 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.00037 | $0.00466 |
| Opus 5 | $0.00018 | $0.00233 |
| Sonnet 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 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
/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.
- yesterday First seen · 46 lines · 37 tokens per session scan A 0ea8ef2b63a9
refactor is a skill published in the GitHub repository kint4/autoframe (6 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 466 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
tokenless
Use when a task can be delegated through the globally installed Tokenless CLI without directly writing to the workspace; route it to a visible AI provider website to save agent tokens.
tokenless-install
Install, upgrade, repair, and verify Tokenless, its agent skills, and local Playwright runtime. Use only when the user explicitly asks for installation, upgrade, repair, browser sign-in handoff, a failed doctor check, or an installation integrity check.
agent-qa-authoring
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
agent-qa-debug-fix
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of generated fix suggestions.
linggan-talking-cards
将中文或英文口播文案与可选截图拆成 3–10 张 PPT 式演示卡片,输出文字准确的 PNG 卡片、结构化 manifest 和带逐卡口播台词的响应式 HTML 预览页。支持 3:4、16:9、9:16、4:3 四种比例,以及苹果白色毛玻璃、糖果、Obsidian、新丑风等 10 种视觉系统;适用于“口播文案拆解PPT生多图”“把逐字稿做成卡片”“给口播配 slides”“截图放进讲解卡片”“生成多图和预览页”“换一种 PPT 风格”以及修改指定卡片的请求。.
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.