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 hzijad/playwright-agent-skills --skill playwright-debugginggit clone --depth 1 https://github.com/hzijad/playwright-agent-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/hzijad/playwright-agent-skills/playwright-debugging)<a href="https://agentmods.dev/skills/hzijad/playwright-agent-skills/playwright-debugging"><img src="https://agentmods.dev/badge/skills/hzijad/playwright-agent-skills/playwright-debugging.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.00026 | $0.01448 |
| Opus 5 | $0.00013 | $0.00724 |
| Sonnet 5 | $0.00005 | $0.00290 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
playwright-debugging 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 6d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Debugging
Flaky Test Diagnosis and Repair
Overview
Use this skill when a Playwright test fails intermittently, behaves differently in CI, or passes locally but not in a repeatable way. The goal is to identify the specific cause of the failure before changing the test.
Use this skill as the first stop for failures. It is not a rewrite guide and it is not a replacement for playwright-core when the test still needs normal authoring discipline.
This skill focuses on four common failure classes: timing and readiness issues, state bleed between tests, hydration or rendering gaps in SPA frameworks, and flakiness that only appears under CI's specific constraints.
Do not use this skill to redesign a test from scratch unless the current test is beyond repair or the user explicitly asks for a rewrite.
When to Use
- When a test fails only in CI or only on some runs.
- When a click, assertion, or navigation happens before the UI is ready.
- When a test depends on data, cookies, or local storage left behind by another test.
- When the app renders before it becomes interactive.
When Not to Use
- When you are writing a new test from scratch.
- When the current test is already stable and the task is just to add new coverage.
- When the app behavior itself needs redesign rather than a narrow test repair.
Diagnostic Workflow
Start with evidence. Use the failing error, the trace viewer, or the exact step that failed before choosing a fix.
- Capture the terminal error or the trace step that failed.
- Decide whether the failure is caused by timing, state bleed, hydration, or a CI-only constraint.
- Fix the narrowest failing line first.
- Verify the fix with a repeatable run, not a single green pass.
If the failing step is ambiguous, inspect the trace before editing. Do not generalize from one red run.
Common Failure Modes
Timing and Readiness
The UI is present, but the app is not ready for interaction yet. In this case, wait for the state the user would observe, not for an arbitrary timer.
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.
- 6d ago First seen · 142 lines · 26 tokens per session scan A bd4d1840f1aa
playwright-debugging is a skill published in the GitHub repository hzijad/playwright-agent-skills (8 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,448 once invoked, about $0.0001 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
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
133-java-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only, and AT classes run by…
323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for…
423-frameworks-quarkus-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock…
132-java-testing-integration-testing
Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with…
322-frameworks-spring-boot-testing-integration-tests
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code…