create-regression-test

create-regression-test is a skill for Claude Code, Codex from agentmantis/test-skills. It costs 76 tokens per session (1,373 once invoked), scanned A, original, MIT.

A test-scaffolding workflow for Playwright, a browser-based end-to-end testing tool. It creates regression or smoke test specifications along with test data and fixture changes.

In plain words
What is it for?
Use it to add regression or smoke tests for a feature, create missing test data or page objects, update fixtures, and run the resulting Playwright test.
Why use it?
It removes the repeated setup work needed to connect a test to page objects, sample data, shared fixtures, cleanup, and parallel-safe execution.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/agentmantis/test-skills/create-regression-test
Any agent
npx skills add agentmantis/test-skills --skill create-regression-test
Clone the repo
git clone --depth 1 https://github.com/agentmantis/test-skills

Made for: Claude Code, Codex.

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 create-regression-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentmantis/test-skills/create-regression-test.svg)](https://agentmods.dev/skills/agentmantis/test-skills/create-regression-test)
Your own site
<a href="https://agentmods.dev/skills/agentmantis/test-skills/create-regression-test"><img src="https://agentmods.dev/badge/skills/agentmantis/test-skills/create-regression-test.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,373 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00076 $0.01373
Opus 5 $0.00038 $0.00687
Sonnet 5 $0.00015 $0.00275
Haiku 4.5 $0.00008 $0.00137

Measured 3d ago against content hash f947249d796a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-regression-test 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 3d 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.

skills/create-regression-test/SKILL.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Regression / Smoke Test

Generate a complete test spec with associated test data and fixture integration.


Workflow

  1. Determine the feature name from the user's request
  2. Determine the suite — regression (default) or smoke
  3. Check if a POM exists in e2e/poms/{feature}.page.ts
    • If yes, read its public methods and JSDoc to understand available actions
    • If no, create one first using the create-pom skill
  4. Check if test data exists in e2e/test-data/{feature}.json
    • If yes, read and use the existing data shape
    • If no, create the JSON file with template data
  5. Check fixtures in e2e/fixtures/base.ts
    • If the feature is not yet registered, add the interface and loader
  6. Create the spec file in the appropriate directory
  7. Run the test to verify it passes:
    npx playwright test --project="chromium:regression" {feature}.spec.ts
    

Spec File Structure

Every spec follows this exact pattern:

import { test } from '../../fixtures/base';
import { getAuthFilePath } from '../../helpers/env-config';
import { FeaturePage } from '../../poms/feature.page';

const authFile = getAuthFilePath();

test.describe('Feature Name Tests', () => {
    // One-time setup: clean stale data from previous failed runs
    test.beforeAll(async ({ browser }) => {
        const context = await browser.newContext({
            storageState: authFile,
        });
        const page = await context.newPage();
        const pom = new FeaturePage(page);
        await pom.setUp();
        await page.close();
        await context.close();
    });

    test('should create a new item', async ({ page, testData }) => {
        const pom = new FeaturePage(page);
        const item = testData.feature.items[0];

        await pom.navigateToPage();
        await pom.createItem(item.name, item.value);
        await pom.verifyItemExists(item.name);
    });

    test('should edit an existing item', async ({ page, testData }) => {
        const pom = new FeaturePage(page);
        const item = testData.feature.items[0];
        const updated = testData.feature.updatedItem;

        await pom.navigateToPage();
        await pom.createItem(item.name, item.value);
        await pom.editItem(item.name, updated.name, updated.value);
        await pom.verifyItemExists(updated.name);
    });

    test('should delete an item', async ({ page, testData }) => {
        const pom = new FeaturePage(page);
        const item = testData.feature.items[1];

        await pom.navigateToPage();
        await pom.createItem(item.name, item.value);
        await pom.deleteItem(item.name);
        await pom.verifyItemNotExists(item.name);
    });
});

Read the full file on GitHub · 173 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago First seen · 173 lines · 76 tokens per session scan A f947249d796a

Subscribe to this mod's changes

create-regression-test is a skill published in the GitHub repository agentmantis/test-skills (12 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 1,373 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

playwright-validation

Use when validating UI changes in a branch require Playwright E2E testing. Reviews branch changes, validates UI with Playwright MCP, and adds missing test cases.

open-metadata/OpenMetadata · 37 tokens

feature-walkthrough

Autonomously test the running binance-trading-bot app in a real browser. The agent drives the browser itself via the Playwright MCP - logs in, looks at each screen, and works through every feature end-to-end like a real operator, finding and fixing bugs. Use when asked to test the app, smoke-test or walk through the…

chrisleekr/binance-trading-bot · 94 tokens

playwright-screen-recording

Record browser test videos with Playwright for PR review and bug fix verification.

liaohch3/claude-tap · 20 tokens

browser-smoke-review

Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.

fallow-rs/fallow · 49 tokens

web-preview

Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.

K9i-0/ccpocket · 32 tokens