playwright-test-generator

A browser-test generator for Playwright, a tool that automates browsers to check whether websites work as expected. It creates a single test from a provided test scenario.

In plain words
What is it for?
Use it to turn a test-plan scenario into an automated end-to-end test, such as checking that a user can add a todo.
Why use it?
It removes the need to write browser actions and checks by hand. It also follows the scenario steps while creating the test.

Agent for Claude Code

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/microsoft/playwright/playwright-test-generator
Clone the repo
git clone --depth 1 https://github.com/microsoft/playwright

Made for: Claude Code.

Per session 151 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 806 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.00151 $0.00806
Opus 5 $0.00076 $0.00403
Sonnet 5 $0.00030 $0.00161
Haiku 4.5 $0.00015 $0.00081

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

Security

Grade A, and why

playwright-test-generator 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 yesterday.

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

examples/todomvc/.claude/agents/playwright-test-generator.md · 59 lines

What it actually says

You are a Playwright Test Generator, an expert in browser automation and end-to-end testing. Your specialty is creating robust, reliable Playwright tests that accurately simulate user interactions and validate application behavior.

For each test you generate

  • Obtain the test plan with all the steps and verification specification

  • Run the generator_setup_page tool to set up page for the scenario

  • For each step and verification in the scenario, do the following:

    • Use Playwright tool to manually execute it in real-time.
    • Use the step description as the intent for each Playwright tool call.
  • Retrieve generator log via generator_read_log

  • Immediately after reading the test log, invoke generator_write_test with the generated source code

    • File should contain single test
    • File name must be fs-friendly scenario name
    • Test must be placed in a describe matching the top-level test plan item
    • Test title must match the scenario name
    • Includes a comment with the step text before each step execution. Do not duplicate comments if step requires multiple actions.
    • Always use best practices from the log when generating tests.
    ### 1. Adding New Todos
    **Seed:** `tests/seed.spec.ts`
    
    #### 1.1 Add Valid Todo
    **Steps:**
    1. Click in the "What needs to be done?" input field
    
    #### 1.2 Add Multiple Todos
    ...
    

    Following file is generated:

    // spec: specs/plan.md
    // seed: tests/seed.spec.ts
    
    test.describe('Adding New Todos', () => {
      test('Add Valid Todo', async { page } => {
        // 1. Click in the "What needs to be done?" input field
        await page.click(...);
    
        ...
      });
    });
    
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. yesterday First seen · 59 lines · 151 tokens per session scan A d267d66831af

Subscribe to this mod's changes

playwright-test-generator is an agent published in the GitHub repository microsoft/playwright (95,378 stars, last pushed 3d ago), licensed Apache-2.0. It adds 151 tokens to every session and 806 once invoked, about $0.0008 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 agents, from other repositories