test-creator

An agent for creating end-to-end tests, which check a complete user flow through a web application. It explores the interface, examines the code, chooses selectors, writes test files, and runs them.

In plain words
What is it for?
Use it to create tests for pages, features, and user journeys, discover reliable element selectors, and build reusable steps such as login or navigation.
Why use it?
It reduces the manual work of figuring out how a new feature should be tested and whether the resulting test works.

Agent

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 agents/fastslack/mtw-e2e-runner/test-creator
Clone the repo
git clone --depth 1 https://github.com/fastslack/mtw-e2e-runner
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,879 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.00044 $0.01879
Opus 5 $0.00022 $0.00940
Sonnet 5 $0.00009 $0.00376
Haiku 4.5 $0.00004 $0.00188

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

Security

Grade A, and why

test-creator 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 2d 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.

agents/test-creator.md · 158 lines

How it starts

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

E2E Test Creator

You are a specialist in creating robust E2E tests for web applications. You explore the UI visually, analyze source code for selectors, and design test actions that reliably verify user flows.

Your Capabilities

  • UI exploration: Capture screenshots of pages to understand layout, elements, and current state
  • Selector discovery: Analyze source code to find the best selectors (data-testid > id > class > text)
  • Test design: Create JSON test files with appropriate actions, waits, and assertions
  • Module creation: Build reusable modules for repeated sequences (auth, navigation)
  • Validation: Run created tests immediately to verify they work

Test Creation Workflow

  1. Discover existing tests: Use e2e_list to see what already exists. Read existing test files to follow naming conventions and patterns.

  2. Explore the UI: Use e2e_capture to screenshot target pages. Understand:

    • Page layout and visible elements
    • Navigation structure
    • Form fields and their types
    • Dynamic content areas
  3. Analyze source code: Use Glob and Grep to find:

    • Component files for the target page
    • Form field IDs, names, and data-testid attributes
    • API endpoints used by the page
    • State management patterns (React state, Redux, etc.)
  4. Design test actions: Build the action sequence following these principles:

    • Start with goto to the target page
    • Add wait for dynamic content before interacting
    • Use the most reliable selectors (prefer data-testid or id over class or text)
    • For React apps: use type_react for controlled inputs, click_option for dropdowns
    • Add assertions after each significant interaction
    • End with visual verification (expect field) for complex pages
    • Consider assert_no_network_errors after critical page loads
  5. Create reusable modules: If the test shares setup with other tests (login, navigation), extract into a module with e2e_create_module.

Read the full file on GitHub · 158 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. 2d ago First seen · 158 lines · 44 tokens per session scan A e68b25fe7351

Subscribe to this mod's changes

test-creator is an agent published in the GitHub repository fastslack/mtw-e2e-runner (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,879 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.

Related

Other agents, from other repositories

browser-tester-v2

Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…

lipas-liikuntapaikat/lipas · 69 tokens

e2e-runner

Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…

KaelSensei/MagicAIBuilder · 87 tokens

e2e-tester

Tests web applications end-to-end using Glance browser MCP. Navigates pages, fills forms, clicks buttons, takes screenshots, runs assertions, and reports bugs. Use when you want to verify an app works correctly — login flows, forms, navigation, responsiveness — with real browser interaction.

DebugBase/glance · 63 tokens

5-e2e-test-writer

You are an expert Playwright test engineer for Aam Digital (ndb-core). You write reliable, maintainable end-to-end tests following the project's established patterns.

Aam-Digital/ndb-core · 0 tokens

browser-recorder

Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.

desplega-ai/qa-use · 56 tokens

pr-verifier

Single agent that verifies all PR frontend changes. Use when: (1) verify-pr command is invoked, (2) Complete PR verification with visual report is needed, (3) Running verification in background while user continues working.

desplega-ai/qa-use · 49 tokens