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 skills add petrkindlmann/qa-skills --skill playwright-automationgit clone --depth 1 https://github.com/petrkindlmann/qa-skillsWrote 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/skills/petrkindlmann/qa-skills/playwright-automation)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/playwright-automation"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/playwright-automation/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/skills/petrkindlmann/qa-skills/playwright-automation"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/playwright-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00177 | $0.05474 |
| Opus 5.5 | $0.00071 | $0.02190 |
| Sonnet 5.5 | $0.00035 | $0.01095 |
| Haiku 4.5 | $0.00018 | $0.00547 |
Grade A, and why
playwright-automation 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 3d 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Questions
Check .agents/qa-project-context.md first — if it exists, use it and skip any question answered there. Then ask only what's missing:
- TypeScript or JavaScript? Match what the project already uses. For a new suite TypeScript is strongly recommended — it catches locator and assertion mistakes at compile time, and the examples here use it. In a JavaScript project or a fixed
.mjsharness, write plain ESM with the same patterns (drop the type annotations), and check it withnode --checkand--listinstead oftsc. - Which browsers? Chromium for local dev; add Firefox and WebKit in CI. Mobile viewports are separate Playwright projects, not separate test files — they change the device descriptor.
- Existing suite or fresh start? Migrating from Cypress/Selenium, rewrite the flakiest tests first; never big-bang. Changes the sequencing entirely.
- Single site or multi-site? Multi-site needs shared fixtures and per-site config objects — see
references/multi-site-architecture.md.
Core Principles
- User-facing locators first.
getByRole>getByLabel>getByTestId> CSS (last resort). Text and label matching is a case-insensitive substring by default, sogetByLabel('Password')also matches "New password" and "Confirm password", hidden fields included, and fails strict mode; pass{ exact: true }when labels share words. Locators must reflect what the user sees, not how the DOM is structured. Seereferences/selector-strategies.md. - Auto-waiting — NEVER use
waitForTimeout. Every Playwright action and web-first assertion auto-waits. If you think you need a timeout, you need a better locator or assertion. - Test isolation. Each test gets a fresh
BrowserContext, but this does not isolate server-side accounts, carts, orders or password changes. Allocate independent records/accounts or a fresh database where tests mutate shared state. Tests must not depend on execution order. - Parallel by default, serial only when necessary. Use
fullyParallel: true. Reservetest.describe.serialfor flows that genuinely cannot be isolated (rare). - Fixtures for setup, not hooks. Fixtures compose, provide type safety, and tear down automatically. Prefer them over
beforeEach/afterEachfor anything non-trivial. Seereferences/fixtures-and-projects.md.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/anti-patterns.md 14 KB
- references/auth-patterns.md 12 KB
- references/ci-recipes.md 12 KB
- references/debugging-and-triage.md 9.6 KB
- references/fixtures-and-projects.md 14 KB
- references/multi-site-architecture.md 13 KB
- references/network-and-mocking.md 13 KB
- references/selector-strategies.md 12 KB
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.
- 3d ago Changed · +1 lines 122994986aee
- 5d ago Changed · +17 lines · -5 tokens per session ca3142f0ed93
- 1mo ago First seen · 461 lines · 182 tokens per session scan A f2ece1d2ab09
playwright-automation is a skill published in the GitHub repository petrkindlmann/qa-skills (210 stars, last pushed 3d ago), licensed MIT. It adds 177 tokens to every session and 5,474 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.
Geb Testing
Browser automation testing with Geb framework for Groovy/JVM using jQuery-like content DSL, Page Object pattern, Spock integration, and WebDriver abstraction.
playwright-e2e
Comprehensive end-to-end testing skill using Playwright for web applications, covering page objects, selectors, assertions, waits, fixtures, and test organization.
e2e-testing-claude-code
Make Claude Code write and maintain end-to-end tests like a senior SDET — Playwright and Cypress flows with stable locators, the Page Object Model, fixtures, reused auth state, network mocking, and flake-free CI. Claude Code E2E testing, done right.
Browser Agent QA Testing
Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.