autoframe: Skill for Claude Code

.claude/skills/new-spec/SKILL.md

new-spec is a skill for Claude Code from kint4/autoframe. It costs 40 tokens per session (561 once invoked), scanned A, original, MIT.

A generator for Playwright browser tests for a feature or page, including normal use, invalid situations, and edge cases. Edge cases are unusual inputs or conditions that can expose hidden problems.

In plain words
What is it for?
Use it with a feature name, page object, or user flow to produce a test file with grouped cases and Arrange/Act/Assert sections.
Why use it?
It creates a consistent test structure so important scenarios are covered without writing the initial test organization by hand.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is kint4/autoframe's own configuration. It tells Claude Code how to work on autoframe itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything autoframe configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/kint4/autoframe/main/.claude/skills/new-spec/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kint4/autoframe

Made for: Claude Code.

Wrote 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.

agentmods badge for new-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/kint4/autoframe/new-spec/github.svg)](https://agentmods.dev/skills/kint4/autoframe/new-spec)
Your own site
<a href="https://agentmods.dev/skills/kint4/autoframe/new-spec"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/new-spec/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.

agentmods 80×15 button for new-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/kint4/autoframe/new-spec"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/new-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00561
Opus 5.5 $0.00016 $0.00224
Sonnet 5.5 $0.00008 $0.00112
Haiku 4.5 $0.00004 $0.00056

Measured 2mo ago against content hash 9edf8414f4fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/skills/new-spec/SKILL.md · 52 lines

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 page with a TODO: create fixture comment
  • test.describe grouping: Happy Path, Negative Cases, Edge Cases
  • Arrange / Act / Assert comments in every test
  • Test names written in plain language

Step-by-Step Instructions

  1. Read the spec conventions in CLAUDE.md.
  2. Locate the relevant Page Object under pages/[feature-name]/. If none exists, recommend /new-page first.
  3. Check fixtures/ for a matching fixture. Use it if present; otherwise fall back to raw page and add the TODO comment.
  4. Write the spec:
    • test.describe('[Feature Name]') as the outer block.
    • beforeEach for setup (navigate / reset state), afterEach for 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 beforeEach inside each inner describe block instead of at the top level.
    • Inner test.describe blocks 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.
  5. Save to tests/e2e/[feature-name]/[feature].spec.ts.
  6. Suggest /review-spec to validate assertion quality.

Rules

  • No logic inside test.describe blocks — only inside test blocks.
  • Always use Arrange / Act / Assert.
  • Prefer custom fixtures over raw page whenever a fixture exists.
  • Drive the page through Page Object methods, not raw locators in the spec.

Read the full file on GitHub · 52 lines

Changes

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.

  1. 2mo ago First seen · 52 lines · 40 tokens per session scan A 9edf8414f4fe

Subscribe to this mod's changes

new-spec is a skill published in the GitHub repository kint4/autoframe (8 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 561 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.