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 YuDefine/nuxt-supabase-starter --skill playwright-best-practicesgit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/yudefine/nuxt-supabase-starter/playwright-best-practices)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/playwright-best-practices"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/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/yudefine/nuxt-supabase-starter/playwright-best-practices"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/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.00214 | $0.04919 |
| Opus 5.5 | $0.00086 | $0.01968 |
| Sonnet 5.5 | $0.00043 | $0.00984 |
| Haiku 4.5 | $0.00021 | $0.00492 |
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 2mo 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
100% identical to playwright-best-practices — 0 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 — 304 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 15 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.
- 2mo ago First seen · 304 lines · 214 tokens per session scan A 42684b93abd5
playwright-best-practices is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (44 stars, last pushed today), licensed MIT. It adds 214 tokens to every session and 4,919 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to playwright-best-practices, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.
validate-fix
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.
investigate-bug
Investigate a bug or issue by exploring the codebase to find root cause, then write a TDD-based fix plan to specs/bugs/BUG-.md. Use when user reports a bug, wants to investigate a problem, mentions "triage", or wants to plan a fix.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
debugging
Systematic debugging and error recovery for Laravel and PHP projects — a five-step triage that goes reproduce, localise, reduce, fix, guard. Covers reading a stack trace properly, bisecting with git, isolating a failure to the smallest reproducer, telling a symptom apart from a root cause, and closing every fix with a…
polya-fix
Phase 5 of the Pólya Heuristic Coder: First-Principles Bug Remediation, Seam Tracing, Bisection Search (O(log n)), Failing Reproduction Tests, and Incubation Circuit-Breaker Gate (docs/bug-reports/{slug}-bugfix.md).