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/setup/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/setup)<a href="https://agentmods.dev/skills/kint4/autoframe/setup"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/setup/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/setup"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/setup.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.00055 | $0.00663 |
| Opus 5.5 | $0.00022 | $0.00265 |
| Sonnet 5.5 | $0.00011 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
setup 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup — Bootstrap the Autoframe Project
Type: Setup Description: Bootstraps the entire Autoframe framework for a specific product. Asks for the app URL, auth type, stack details, and CI platform, then produces a fully wired, ready-to-run Playwright project. Includes a simple mode for non-technical users.
Input Format
The user runs /setup. Gather the following before generating anything:
- App URL — the base URL of the product under test (
BASE_URL) - API URL — base URL for API tests, if any (
API_URL) - Auth type — none / form login / token / SSO
- First feature to cover — e.g.
auth,checkout - CI platform — defaults to GitHub Actions
If the user signals they are non-technical (Persona 1 or 4), switch to simple mode: ask only for the app URL and what they want to test first, and explain each step in plain language.
Output Format
A fully scaffolded project that matches the folder structure in CLAUDE.md, with:
playwright.config.ts,tsconfig.json,package.json.env.examplepopulated with the discovered variables.gitignore- The three GitHub Actions workflows (
e2e.yml,api.yml,load.yml) - One starter Page Object, spec, and fixture for the first feature
- A short summary of what was created and how to run it
Step-by-Step Instructions
- Read
CLAUDE.mdandAUTOFRAME.mdcompletely. - Detect the persona from the user's language (see CLAUDE.md). Adjust tone and depth.
- Ask the clarifying questions above (max 3 at a time). In simple mode, ask the minimum.
- Verify the folder structure exists; create any missing directories exactly as defined in CLAUDE.md.
- Generate or confirm the baseline config files. Never substitute the stack.
- Write
.env.examplewith every required variable (BASE_URL,API_URL,API_TOKEN,TEST_USER_EMAIL,TEST_USER_PASSWORD). Never write a real.env. - Generate a starter Page Object + spec + fixture for the first feature, following the POM and spec conventions exactly.
- Confirm the three CI workflows exist.
- Summarize what was created and give the exact commands to install and run (
npm install,npx playwright install,npm test). - Suggest the next skill to run (usually
/new-pageor/tc-to-spec).
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 · 53 lines · 0 tokens per session scan A a46702eef43d
setup is a skill published in the GitHub repository kint4/autoframe (8 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 663 once invoked, about $0.0002 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
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.
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.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
playwright-trace
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.