Playwright is a framework for automating and testing websites through one API that drives Chromium, Firefox, and WebKit. Developers use it for end-to-end tests, browser automation scripts, and AI-agent web interactions. The catalogue add-ons help coding and AI agents use Playwright for testing and browser automation.
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.
git clone --depth 1 https://github.com/microsoft/playwrightWrote 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.
[](https://agentmods.dev/commands/microsoft/playwright/playwright-test-plan)<a href="https://agentmods.dev/commands/microsoft/playwright/playwright-test-plan"><img src="https://agentmods.dev/badge/commands/microsoft/playwright/playwright-test-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/microsoft/playwright/playwright-test-plan"><img src="https://agentmods.dev/badge/commands/microsoft/playwright/playwright-test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00003 | $0.00059 |
| Opus 5.5 | $0.00001 | $0.00024 |
| Sonnet 5.5 | $0.00001 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
playwright-test-plan 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 1mo 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.
What it actually says
Create test plan for basic operations of the todo app. Test plan should contain around 20 tests.
- Seed file:
tests/seed.spec.ts - Test plan:
specs/basic-operations.plan.md
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.
- 1mo ago First seen · 10 lines · 3 tokens per session scan A 73e856292fcc
playwright-test-plan is a command published in the GitHub repository microsoft/playwright (98,318 stars, last pushed today), licensed Apache-2.0. It adds 3 tokens to every session and 59 once invoked, about $0.0000 per session on Opus 5.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-09-08.
Other commands, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
qawolfCliRunResults.template
How to use what qawolf run get --run-id --json returns, and how to read the Playwright trace it links to.
generate
Generate maintainable pytest tests from a URL or mobile screen via mk-qa-master's analyzer.
test-run
Run E2E tests with qa-use CLI.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
verify
Final verification - run all Pest tests, validate Playwright UI flows, and check production checklist.