playwright-test-generator

playwright-test-generator is an agent for coding agents from priyshi/playwright_mcp_pr. It costs 151 tokens per session (803 once invoked), scanned A, a copy of playwright-test-generator, Apache-2.0.

An agent that creates automated browser tests with Playwright, a tool for controlling a real browser and checking what an application does.

In plain words
What is it for?
Setting up a test page, carrying out the planned interactions, recording the test process, and writing one Playwright test file for the scenario.
Why use it?
It turns a written test scenario into a repeatable test while checking each step in the browser first.

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

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/priyshi/playwright_mcp_pr/playwright-test-generator.svg)](https://agentmods.dev/agents/priyshi/playwright_mcp_pr/playwright-test-generator)
Your own site
<a href="https://agentmods.dev/agents/priyshi/playwright_mcp_pr/playwright-test-generator"><img src="https://agentmods.dev/badge/agents/priyshi/playwright_mcp_pr/playwright-test-generator.svg" alt="Measured on agentmods" height="20"></a>
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 803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00151 $0.00803
Opus 5 $0.00076 $0.00402
Sonnet 5 $0.00030 $0.00161
Haiku 4.5 $0.00015 $0.00080

Measured 5d ago against content hash 943b6e4c1185, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 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.

Origin

This is a copy

88% identical to playwright-test-generator — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/playwright-test-generator.agent.md · 96 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. 5d ago First seen · 96 lines · 151 tokens per session scan A 943b6e4c1185

Subscribe to this mod's changes

playwright-test-generator is an agent published in the GitHub repository priyshi/playwright_mcp_pr (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 151 tokens to every session and 803 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to playwright-test-generator, differing in 31 lines, and is treated as a copy.

Related

Other agents, from other repositories

qa

Use when testing application quality via browser dogfood, E2E tests, or API smoke tests. Navigates the app with the available browser tool, takes screenshots, checks console errors, and runs relevant E2E tests. Read-only — reports issues but never edits code. Also use when the user says 'test this', 'dogfood', 'QA'…

exceptionless/Exceptionless · 85 tokens

playwright-test-generator

Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…

SigNoz/signoz · 0 tokens

testing

Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).

windviki/vBookmarks · 0 tokens

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

qa

Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…

sheshbabu/zen · 0 tokens

visual-tester

Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.

HazAT/pi-interactive-subagents · 28 tokens