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.
npx agentmods add agents/microsoft/playwright/playwright-test-plannergit clone --depth 1 https://github.com/microsoft/playwrightWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00023 | $0.00617 |
| Opus 5 | $0.00012 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00062 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- playwright-test-planner — 100% identical, 4 lines differ
- playwright-test-planner — 97% identical, 2 lines differ
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:
-
Navigate and Explore
- Invoke the
planner_setup_pagetool 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
- Invoke the
-
Analyze User Flows
- Map out the primary user journeys and identify critical paths through the application
- Consider different user types and their typical behaviors
-
Design Comprehensive Scenarios
Create detailed test scenarios that cover:
- Happy path scenarios (normal user behavior)
- Edge cases and boundary conditions
- Error handling and validation
-
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
-
Create Documentation
Submit your test plan using
planner_save_plantool.
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.
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.
- yesterday First seen · 52 lines · 23 tokens per session scan A fe875b460221
playwright-test-planner is an agent published in the GitHub repository microsoft/playwright (95,378 stars, last pushed 3d ago), licensed Apache-2.0. It adds 23 tokens to every session and 617 once invoked, about $0.0001 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.
Other agents, from other repositories
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.
adrian
Blocks until a tmux pane is done (pattern match, shell idle, or output idle). Use for any wait that takes more than a few seconds.
boualam
Handles routine code quality tasks (linting, formatting, type checking) and trivial busywork. Runs iteratively until all checks pass. Use for cleanup tasks you don't want cluttering your main context.
bf-e2e-generator
为指定模块录制选择器并生成 Playwright E2E 测试脚本，能操作浏览器和创建新文件，但不能编辑已有文件或执行测试.
bf-e2e-validator
校验 E2E 测试脚本的断言是否与测试用例预期结果对齐，找出弱断言并修复.
triage-lead
Use this agent to triage the full E2E test suite. Runs all tests, classifies every failure, manages project knowledge (error patterns, flows, triage history), creates tasks, and dispatches investigator/fixer agents. Examples: Context: User wants a full suite health check. user: 'Triage the e2e suite' assistant: 'I…