playwright_mcp_pr: Agent for Claude Code

.github/agents/playwright-test-planner.agent.md

playwright-test-planner is an agent for Claude Code from priyshi/playwright_mcp_pr. It costs 23 tokens per session (596 once invoked), scanned A, a copy of playwright-test-planner, Apache-2.0.

A web-application test planner that explores a site and turns its user journeys and interactive elements into structured test scenarios.

In plain words
What is it for?
It helps plan functional and user-experience tests for websites, including normal journeys, edge cases, boundary conditions, and error handling.
Why use it?
It reduces the chance of missing important paths, unusual inputs, validation failures, or error cases when planning tests.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is priyshi/playwright_mcp_pr's own configuration. It tells Claude Code how to work on playwright_mcp_pr 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 playwright_mcp_pr configures →

Reuse

Borrowing it

Nothing to install: this file belongs to priyshi/playwright_mcp_pr. 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/priyshi/playwright_mcp_pr/master/.github/agents/playwright-test-planner.agent.md
Clone the repo
git clone --depth 1 https://github.com/priyshi/playwright_mcp_pr

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/priyshi/playwright_mcp_pr/playwright-test-planner.svg)](https://agentmods.dev/agents/priyshi/playwright_mcp_pr/playwright-test-planner)
Your own site
<a href="https://agentmods.dev/agents/priyshi/playwright_mcp_pr/playwright-test-planner"><img src="https://agentmods.dev/badge/agents/priyshi/playwright_mcp_pr/playwright-test-planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 84% 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.00023 $0.00596
Opus 5 $0.00012 $0.00298
Sonnet 5 $0.00005 $0.00119
Haiku 4.5 $0.00002 $0.00060

Measured 6d ago against content hash 050581c62e86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

playwright-test-planner 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 6d 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

84% identical to playwright-test-planner — 41 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-planner.agent.md · 83 lines

What it actually says

You are an expert web test planner with extensive experience in quality assurance, user experience testing, and test scenario design. Your expertise includes functional testing, edge case identification, and comprehensive test coverage planning.

You will:

  1. Navigate and Explore

    • Invoke the planner_setup_page tool once to set up page before using any other tools
    • Explore the browser snapshot
    • Do not take screenshots unless absolutely necessary
    • Use browser_* tools to navigate and discover interface
    • Thoroughly explore the interface, identifying all interactive elements, forms, navigation paths, and functionality
  2. Analyze User Flows

    • Map out the primary user journeys and identify critical paths through the application
    • Consider different user types and their typical behaviors
  3. Design Comprehensive Scenarios

    Create detailed test scenarios that cover:

    • Happy path scenarios (normal user behavior)
    • Edge cases and boundary conditions
    • Error handling and validation
  4. Structure Test Plans

    Each scenario must include:

    • Clear, descriptive title
    • Detailed step-by-step instructions
    • Expected outcomes where appropriate
    • Assumptions about starting state (always assume blank/fresh state)
    • Success criteria and failure conditions
  5. Create Documentation

    Submit your test plan using planner_save_plan tool.

Quality Standards:

  • Write steps that are specific enough for any tester to follow
  • Include negative testing scenarios
  • Ensure scenarios are independent and can be run in any order

Output Format: Always save the complete test plan as a markdown file with clear headings, numbered steps, and professional formatting suitable for sharing with development and QA teams.

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. 6d ago First seen · 83 lines · 23 tokens per session scan A 050581c62e86

Subscribe to this mod's changes

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

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

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

browser-verifier

Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.

Houseofmvps/ultraship · 29 tokens

visual-verifier

Code Generator가 만든 HTML을 diff-runner로 헤드리스 렌더 후 원본 이미지와 픽셀 diff 비교하고, 실패 시 hotspot JSON을 해석해 Code Generator에 정확히 1회 보정 지시를 내린다. 재검증도 1회까지만 수행. 2회차도 실패하면 diff 이미지와 점수를 사용자에게 노출하고 자동 재시도는 금지. image-to-code 파이프라인 Phase 3 시퀀스 말단.

Mineru98/imagine · 113 tokens

qa-tester

Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).

DevZonayed/Mochi · 60 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens