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 sutchan/Agent-Skills-Hub --skill playwright-best-practicesgit clone --depth 1 https://github.com/sutchan/Agent-Skills-HubWrote 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/sutchan/agent-skills-hub/playwright-best-practices)<a href="https://agentmods.dev/skills/sutchan/agent-skills-hub/playwright-best-practices"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/playwright-best-practices/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/sutchan/agent-skills-hub/playwright-best-practices"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/playwright-best-practices.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.00176 | $0.05106 |
| Opus 5 | $0.00088 | $0.02553 |
| Sonnet 5 | $0.00035 | $0.01021 |
| Haiku 4.5 | $0.00018 | $0.00511 |
Grade A, and why
playwright-best-practices 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 7d 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.
This is a copy
98% identical to playwright-best-practices — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Best Practices
This skill provides comprehensive guidance for all aspects of Playwright test development, from writing new tests to debugging and maintaining existing test suites.
Activity-Based Reference Guide
Consult these references based on what you're doing:
Writing New Tests
When to use: Creating new test files, writing test cases, implementing test scenarios
| Activity | Reference Files |
|---|---|
| Writing E2E tests | test-suite-structure.md, locators.md, assertions-waiting.md |
| Writing component tests | component-testing.md, test-suite-structure.md |
| Writing API tests | api-testing.md, test-suite-structure.md |
| Writing GraphQL tests | graphql-testing.md, api-testing.md |
| Writing visual regression tests | visual-regression.md, canvas-webgl.md |
| Structuring test code with POM | page-object-model.md, test-suite-structure.md |
| Setting up test data/fixtures | fixtures-hooks.md, test-data.md |
| Handling authentication | authentication.md, authentication-flows.md |
| Testing date/time features | clock-mocking.md |
| Testing file upload/download | file-operations.md, file-upload-download.md |
| Testing forms/validation | forms-validation.md |
| Testing drag and drop | drag-drop.md |
| Testing accessibility | accessibility.md |
| Testing security (XSS, CSRF) | security-testing.md |
| Using test annotations | annotations.md |
| Using test tags | test-tags.md |
| Testing iframes | iframes.md |
| Testing canvas/WebGL | canvas-webgl.md |
| Internationalization (i18n) | i18n.md |
| Testing Electron apps | electron.md |
| Testing browser extensions | browser-extensions.md |
What ships with it
58 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.
- advanced/authentication-flows.md 11 KB
- advanced/authentication.md 30 KB
- advanced/clock-mocking.md 9.6 KB
- advanced/mobile-testing.md 11 KB
- advanced/multi-context.md 8.4 KB
- advanced/multi-user.md 11 KB
- advanced/network-advanced.md 11 KB
- advanced/third-party.md 12 KB
- architecture/pom-vs-fixtures.md 11 KB
- architecture/test-architecture.md 14 KB
- architecture/when-to-mock.md 11 KB
- browser-apis/browser-apis.md 10 KB
- browser-apis/iframes.md 11 KB
- browser-apis/service-workers.md 13 KB
- browser-apis/websockets.md 10 KB
- core/annotations.md 11 KB
- core/assertions-waiting.md 9.2 KB
- core/configuration.md 12 KB
- core/fixtures-hooks.md 12 KB
- core/global-setup.md 13 KB
- core/locators.md 6.4 KB
- core/page-object-model.md 7.9 KB
- core/projects-dependencies.md 8.7 KB
- core/test-data.md 12 KB
- core/test-suite-structure.md 9.3 KB
- core/test-tags.md 6.9 KB
- debugging/console-errors.md 9.9 KB
- debugging/debugging.md 15 KB
- debugging/error-testing.md 9.5 KB
- debugging/flaky-tests.md 15 KB
- frameworks/angular.md 18 KB
- frameworks/nextjs.md 13 KB
- frameworks/react.md 17 KB
- frameworks/vue.md 17 KB
- infrastructure-ci-cd/ci-cd.md 9.8 KB
- infrastructure-ci-cd/docker.md 6.1 KB
- infrastructure-ci-cd/github-actions.md 13 KB
- infrastructure-ci-cd/gitlab.md 10 KB
- infrastructure-ci-cd/other-providers.md 13 KB
- infrastructure-ci-cd/parallel-sharding.md 11 KB
- infrastructure-ci-cd/performance.md 12 KB
- infrastructure-ci-cd/reporting.md 10 KB
- infrastructure-ci-cd/test-coverage.md 12 KB
- testing-patterns/accessibility.md 9.0 KB
- testing-patterns/api-testing.md 24 KB
- testing-patterns/browser-extensions.md 14 KB
- testing-patterns/canvas-webgl.md 13 KB
- testing-patterns/component-testing.md 11 KB
- testing-patterns/drag-drop.md 18 KB
- testing-patterns/electron.md 13 KB
- testing-patterns/file-operations.md 10 KB
- testing-patterns/file-upload-download.md 17 KB
- testing-patterns/forms-validation.md 22 KB
- testing-patterns/graphql-testing.md 8.5 KB
- testing-patterns/i18n.md 13 KB
- testing-patterns/performance-testing.md 12 KB
- testing-patterns/security-testing.md 12 KB
- testing-patterns/visual-regression.md 17 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.
- 7d ago First seen · 306 lines · 176 tokens per session scan A bdcc0dc3e7cc
playwright-best-practices is a skill published in the GitHub repository sutchan/Agent-Skills-Hub (2 stars, last pushed today), licensed MIT. It adds 176 tokens to every session and 5,106 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to playwright-best-practices, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
browser-testing-with-devtools
Use Chrome DevTools MCP to inspect, debug, and verify anything that runs in a browser — DOM structure, console errors, network requests, performance traces, and accessibility. Use when building or fixing browser UI, diagnosing a runtime bug that isn't visible from source code alone, or verifying a fix actually works…
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
verify-bb
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected…
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
maintain-verification-skill
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".