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 agentmods add skills/pproenca/dot-skills/playwrightnpx skills add pproenca/dot-skills --skill playwrightgit clone --depth 1 https://github.com/pproenca/dot-skillsWhat 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 | $0.00069 | $0.01548 |
| Opus 5 | $0.00034 | $0.00774 |
| Sonnet 5 | $0.00014 | $0.00310 |
| Haiku 4.5 | $0.00007 | $0.00155 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- playwright — 92% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright + Next.js Testing Best Practices
Comprehensive testing optimization guide for Playwright with Next.js applications. Contains 43 rules across 8 categories, prioritized by impact to guide reliable, fast, and maintainable E2E tests.
When to Apply
Reference these guidelines when:
- Writing new Playwright tests for Next.js apps
- Debugging flaky or failing tests
- Optimizing test execution speed
- Setting up authentication state reuse
- Configuring CI/CD pipelines for testing
- Testing Server Components and App Router features
- Reviewing test code for reliability issues
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Test Architecture | CRITICAL | arch- |
| 2 | Selectors & Locators | CRITICAL | loc- |
| 3 | Waiting & Assertions | HIGH | wait- |
| 4 | Authentication & State | HIGH | auth- |
| 5 | Mocking & Network | MEDIUM-HIGH | mock- |
| 6 | Next.js Integration | MEDIUM | next- |
| 7 | Performance & Speed | MEDIUM | perf- |
| 8 | Debugging & CI | LOW-MEDIUM | debug- |
Quick Reference
1. Test Architecture (CRITICAL)
arch-test-isolation- Use fresh browser context for each testarch-parallel-execution- Enable parallel test executionarch-page-object-model- Use Page Object Model for complex pagesarch-fixtures- Use fixtures for shared setuparch-test-production- Test against production buildsarch-cleanup-state- Clean up test state after each test
2. Selectors & Locators (CRITICAL)
loc-role-selectors- Use role-based selectors over CSSloc-data-testid- Use data-testid for dynamic elementsloc-label-selectors- Use getByLabel for form inputsloc-text-selectors- Use getByText for static contentloc-avoid-xpath- Avoid XPath selectorsloc-chained-locators- Chain locators for specificityloc-placeholder-selector- Use getByPlaceholder sparingly
What ships with it
47 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.
- AGENTS.md 8.2 KB
- assets/templates/_template.md 1.0 KB
- metadata.json 961 B
- references/_sections.md 1.8 KB
- references/arch-cleanup-state.md 2.5 KB
- references/arch-fixtures.md 2.5 KB
- references/arch-page-object-model.md 2.4 KB
- references/arch-parallel-execution.md 1.6 KB
- references/arch-test-isolation.md 1.7 KB
- references/arch-test-production.md 1.9 KB
- references/auth-api-login.md 2.6 KB
- references/auth-multiple-roles.md 3.2 KB
- references/auth-parallel-workers.md 3.0 KB
- references/auth-session-storage.md 3.2 KB
- references/auth-storage-state.md 2.7 KB
- references/debug-ci-reporters.md 1.9 KB
- references/debug-inspector.md 2.1 KB
- references/debug-screenshots-videos.md 2.0 KB
- references/debug-trace-viewer.md 1.8 KB
- references/loc-avoid-xpath.md 2.1 KB
- references/loc-chained-locators.md 2.2 KB
- references/loc-data-testid.md 2.3 KB
- references/loc-label-selectors.md 2.3 KB
- references/loc-placeholder-selector.md 2.3 KB
- references/loc-role-selectors.md 1.9 KB
- references/loc-text-selectors.md 2.1 KB
- references/mock-abort-requests.md 2.6 KB
- references/mock-api-responses.md 2.5 KB
- references/mock-har-files.md 2.9 KB
- references/mock-intercept-modify.md 2.6 KB
- references/mock-network-conditions.md 2.7 KB
- references/next-app-router-navigation.md 2.7 KB
- references/next-baseurl-config.md 2.6 KB
- references/next-server-actions.md 2.8 KB
- references/next-server-components.md 2.7 KB
- references/next-wait-hydration.md 2.7 KB
- references/perf-browser-selection.md 2.6 KB
- references/perf-headless-ci.md 2.1 KB
- references/perf-retries.md 2.5 KB
- references/perf-reuse-server.md 2.2 KB
- references/perf-sharding.md 2.5 KB
- references/wait-action-retries.md 2.5 KB
- references/wait-avoid-hard-waits.md 2.6 KB
- references/wait-custom-timeout.md 2.4 KB
- references/wait-network-idle.md 2.7 KB
- references/wait-soft-assertions.md 2.8 KB
- references/wait-web-first-assertions.md 2.4 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 First seen · 118 lines · 69 tokens per session scan A 099d77dba430
playwright is a skill published in the GitHub repository pproenca/dot-skills (200 stars, last pushed 18d ago), licensed MIT. It adds 69 tokens to every session and 1,548 once invoked, about $0.0003 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-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.