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 andrewsrigom/agent-skills --skill playwright-debugging-traces-and-flake-reductiongit clone --depth 1 https://github.com/andrewsrigom/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/andrewsrigom/agent-skills/playwright-debugging-traces-and-flake-reduction)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/playwright-debugging-traces-and-flake-reduction"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-debugging-traces-and-flake-reduction/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/andrewsrigom/agent-skills/playwright-debugging-traces-and-flake-reduction"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-debugging-traces-and-flake-reduction.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.00057 | $0.00677 |
| Opus 5 | $0.00028 | $0.00338 |
| Sonnet 5 | $0.00011 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
playwright-debugging-traces-and-flake-reduction 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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Debugging Traces And Flake Reduction
Use this skill when the problem is unreliable test behavior or poor observability during failure analysis.
Scope
- trace viewer
- inspector and UI mode
- codegen as a debugging aid
- CI-only flake investigation
- turning failures into explicit synchronization or contract fixes
Routing cues
- flaky tests, CI-only failures, trace viewer,
show-trace, UI mode, inspector,PWDEBUG, codegen, or finding the real source of instability -> use this skill - if the issue is clearly just a bad locator or weak assertion -> use
playwright-locators-assertions-and-user-visible-contracts - if the issue is clearly auth reuse or stale storage state -> use
playwright-auth-projects-and-isolation - if the issue is clearly backend timing or mocking boundaries -> use
playwright-network-control-and-api-synchronization
Default path
- Reproduce the failure with traces enabled.
- Inspect the failing step in Trace Viewer before changing the test.
- Use UI mode or inspector when an interactive run clarifies the timing or locator issue.
- Use codegen only to discover robust locators or interaction flow, then clean the generated code aggressively.
- Fix the root contract: locator, assertion, synchronization, auth state, or environment setup.
When to deviate
- Increase trace capture only when the existing signal is insufficient.
- Use video or screenshot artifacts when traces alone do not explain a visual issue.
- Add targeted debug logging only when the trace and inspector still leave the failure ambiguous.
Guardrails
- investigate before changing retries
- codegen output is raw material, not final test code
- flake fixes should remove ambiguity, not just slow the test down
- CI-only failures usually mean environment or synchronization drift, not just “bad luck”
Avoid
- bumping retries first and calling the flake solved
- committing codegen output unchanged
- adding blanket waits because the trace was not inspected
- treating one passing rerun as proof the test is healthy
What ships with it
1 file 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.
- 10d ago First seen · 77 lines · 57 tokens per session scan A fc527dda504d
playwright-debugging-traces-and-flake-reduction is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 677 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-31.
Other skills, from other repositories
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
reality-verification
This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
qa
Read-only automated QA sweep of a deployed stardust site on AEM Edge Delivery Services — validates routing, content fidelity vs the source capture, template conformance, rendered integrity (geometry, JS errors, broken images), visual regression vs baselines, metadata/SEO/JSON-LD, link integrity, accessibility (axe)…
flutter-skill
Automate and test Flutter applications — launch apps, inspect widgets, tap elements, enter text, scroll, swipe, take screenshots, validate state, and debug via Dart VM Service Protocol. Use when the user wants to run Flutter app tests, automate Flutter UI interactions, inspect widget trees, debug a running Flutter…