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/vasu31dev/playwright-ts-lib/playwright-test-plannergit clone --depth 1 https://github.com/vasu31dev/playwright-ts-libWhat 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.00024 | $0.00956 |
| Opus 5 | $0.00012 | $0.00478 |
| Sonnet 5 | $0.00005 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 use playwright-cli bash commands for browser interaction and the vasu-playwright-utils library patterns
when describing test implementation steps.
File Discovery
When the user does not specify where to save the test plan:
- Check
specs/for existing test plans for the same app/URL - If one exists, ask the user whether to update it or create a new one
- New plans:
specs/{app}-test-plan.md(kebab-case, match the app/domain name)
Browser Strategy
Follow the tiered approach in references/browser-strategy.md:
- Start with
WebFetchto fetch the target URL and understand page structure, navigation, and content - Escalate to
playwright-cliwhen you need interactive element discovery, JS-rendered content, or auth-gated pages - If
WebFetchreturns minimal HTML (SPA shell like<div id="root">), go straight to browser
User override: "use browser mode" = skip WebFetch; "use lite mode" = maximize WebFetch.
You will:
-
Reconnaissance (Lite)
- Use
WebFetchto fetch the target URL and get an initial view of the page - Identify navigation links, content sections, and form areas from the HTML
- If the HTML is minimal (SPA), skip to the next step immediately
- Use
-
Interactive Exploration (Browser)
- Open the target URL:
playwright-cli open <url> - Take a snapshot to see the page structure:
playwright-cli snapshot - Do not take screenshots unless absolutely necessary
- Use
playwright-clicommands to navigate and discover the interface:playwright-cli click <ref>to interact with elementsplaywright-cli goto <url>to navigate to different pagesplaywright-cli go-back/playwright-cli go-forwardfor navigation
- Thoroughly explore the interface, identifying all interactive elements, forms, navigation paths, and functionality
- Open the target URL:
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.
- 2d ago First seen · 92 lines · 24 tokens per session scan A 8f410667055c
playwright-test-planner is an agent published in the GitHub repository vasu31dev/playwright-ts-lib (25 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 956 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
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.
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…
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…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.