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 testdino-hq/playwright-skill --skill qagit clone --depth 1 https://github.com/testdino-hq/playwright-skillWrote 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/testdino-hq/playwright-skill/qa)<a href="https://agentmods.dev/skills/testdino-hq/playwright-skill/qa"><img src="https://agentmods.dev/badge/skills/testdino-hq/playwright-skill/qa/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/testdino-hq/playwright-skill/qa"><img src="https://agentmods.dev/badge/skills/testdino-hq/playwright-skill/qa.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.00083 | $0.00475 |
| Opus 5.5 | $0.00033 | $0.00190 |
| Sonnet 5.5 | $0.00017 | $0.00095 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
playwright-qa 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.
What it actually says
Playwright QA Workflows
For QA engineers: the work around the test code. What to test, how to report what broke, how to automate a manual suite, and how to judge a test.
4 guides. They build on the core/ guides for the Playwright APIs and link to them rather than repeating them.
Guide Index
| What you're doing | Guide |
|---|---|
| Ticket / PRD / acceptance criteria → test cases, risk ranking, test plan for the generator | test-design.md |
| Failing test → app bug, test bug or flake; bug report; what to do with the test meanwhile | bug-reports.md |
| Manual test cases or a CSV export → Playwright specs with case IDs | manual-to-automated.md |
| Review Playwright tests or a PR; lint rules; prove a test can fail | test-review.md |
Golden Rules
- Boundaries and negative paths first: bugs live at the edges of a rule, not in the happy path.
- Lowest layer that proves it: rules at API level, wiring and critical flows in E2E.
- Classify before filing: app bug, test bug, flake or environment; the trace usually decides.
- Frequency is a number:
--repeat-each=20gives N/20, never "sometimes". - Known bug →
test.fail()with an issue link, never a deleted test or a loosened assertion. - A test that can't fail guards nothing: break the feature once and watch it fail.
- Keep case IDs on automated tests so results map back to the manual suite.
What ships with it
4 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.
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 First seen · 30 lines · 83 tokens per session scan A e41db42fb3b7
playwright-qa is a skill published in the GitHub repository testdino-hq/playwright-skill (395 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 475 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
browser-agent
Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
browser-task-and-automation-and-delegation
A required procedure for browser actions carried out through a separate browser specialist. Browser actions include opening pages, filling forms, taking snapshots, performance checks, automated tests, and data collection.
integration
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
website-change-verifier
Verify website changes across source, routes, rendering, metadata, discovery surfaces, and deployment state. Use when a user asks to check a new or edited page, confirm an exact replacement, validate a route, inspect responsive behavior, verify metadata or sitemap changes, compare localhost with production, or…
frontend-visual-qa
Verify rendered frontend evidence after implementation, including screenshot comparison, responsiveness, overflow, visible states, and scoped visual regression. Use available browser tooling only; exclude static lookup, routine code review, lint, builds, onboarding, and tool detection.
testing-patterns
Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.