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/new-specnpx skills add kint4/autoframe --skill new-specgit 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/new-spec)<a href="https://agentmods.dev/skills/kint4/autoframe/new-spec"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/new-spec.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00561 |
| Opus 5 | $0.00020 | $0.00280 |
| Sonnet 5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
new-spec 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-spec — Generate a Spec File
Type: Functional Description: Generates a Playwright spec file for a given feature or Page Object, with happy path, negative, and edge cases pre-written following Autoframe conventions.
Input Format
The user provides one of:
- A feature name (e.g.
login) - An existing Page Object to test
- A short description of the user flow
Output Format
A spec file at tests/e2e/[feature-name]/[feature].spec.ts that follows the spec conventions in CLAUDE.md:
- Imports from the matching custom fixture when one exists; otherwise raw
pagewith aTODO: create fixturecomment test.describegrouping: Happy Path, Negative Cases, Edge Cases- Arrange / Act / Assert comments in every test
- Test names written in plain language
Step-by-Step Instructions
- Read the spec conventions in CLAUDE.md.
- Locate the relevant Page Object under
pages/[feature-name]/. If none exists, recommend/new-pagefirst. - Check
fixtures/for a matching fixture. Use it if present; otherwise fall back to rawpageand add theTODOcomment. - Write the spec:
test.describe('[Feature Name]')as the outer block.beforeEachfor setup (navigate / reset state),afterEachfor cleanup if needed.- If Negative or Edge cases need different setup than the Happy Path (e.g. an
unauthenticated-access test must skip the login that other tests need), put the
beforeEachinside each innerdescribeblock instead of at the top level. - Inner
test.describeblocks for Happy Path, Negative Cases, Edge Cases. - At least one meaningful test per group; never leave a group empty.
- Arrange / Act / Assert comments in each test body.
- Plain-language test names a non-technical person can read.
- Save to
tests/e2e/[feature-name]/[feature].spec.ts. - Suggest
/review-specto validate assertion quality.
Rules
- No logic inside
test.describeblocks — only insidetestblocks. - Always use Arrange / Act / Assert.
- Prefer custom fixtures over raw
pagewhenever a fixture exists. - Drive the page through Page Object methods, not raw locators in the 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.
- 5d ago First seen · 52 lines · 40 tokens per session scan A 9edf8414f4fe
new-spec is a skill published in the GitHub repository kint4/autoframe (6 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 561 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
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; request automation of…
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.
playwright
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from…
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.