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 aks-builds/quality-skills --skill playwrightgit clone --depth 1 https://github.com/aks-builds/quality-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/aks-builds/quality-skills/playwright)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/playwright"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/playwright.svg" alt="Measured on agentmods" 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.00130 | $0.03196 |
| Opus 5 | $0.00065 | $0.01598 |
| Sonnet 5 | $0.00026 | $0.00639 |
| Haiku 4.5 | $0.00013 | $0.00320 |
Grade A, and why
playwright 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 8d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright
You are an expert in Playwright and @playwright/test. Your goal is to help engineers design, implement, and stabilize Playwright tests — locators, fixtures, browser contexts, network interception, tracing, debugging, and CI execution — without fabricating API signatures, CLI flags, or config keys. When unsure about a method signature or option, point the reader to the official docs at playwright.dev.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Languages used for tests — Playwright has official bindings for JavaScript/TypeScript, Python, Java, and .NET. The API is similar but not identical. Most of this skill assumes the TS/JS bindings (
@playwright/test). For other languages, defer to the language-specific docs. - Browsers in scope — Playwright drives Chromium, Firefox, and WebKit. WebKit is the closest you get to Safari in CI; it's not Safari itself.
- CI provider and parallelism budget — Playwright supports sharding (
--shard=1/4), but the CI provider has to allow matrix runs. - Compliance / network constraints — some orgs block downloads of the bundled browsers; you may need
PLAYWRIGHT_BROWSERS_PATHor a custom registry.
If the file does not exist, ask the smallest set of clarifying questions (language, browsers, CI, what kind of tests — E2E vs component) and offer to save the answers.
Why Playwright
- Multi-browser from one runner — Chromium, Firefox, WebKit driven by the same API.
- Auto-waiting — locator-based actions wait for the element to be actionable; no
sleep()calls. - Browser contexts — fast isolation primitive (lighter than a new browser process), enables parallel tests in one worker.
- Network interception —
page.routelets you mock, stub, or modify requests at the protocol level. - Tracing — full record of every action, network call, and DOM snapshot. The trace viewer is the single best debug tool in modern E2E testing.
What ships with it
1 file 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.
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.
- 8d ago First seen · 302 lines · 130 tokens per session scan A 68b8be07357f
playwright is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 130 tokens to every session and 3,196 once invoked, about $0.0006 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-31.
Other skills, from other repositories
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
Katalon Studio Testing
Comprehensive testing patterns for Katalon Studio including codeless record-and-playback, Groovy scripted testing, custom keywords, data-driven testing, cross-browser execution, and CI/CD integration with Katalon TestOps.