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 agents/vasu31dev/playwright-ts-lib/playwright-test-healergit clone --depth 1 https://github.com/vasu31dev/playwright-ts-libWrote 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/agents/vasu31dev/playwright-ts-lib/playwright-test-healer)<a href="https://agentmods.dev/agents/vasu31dev/playwright-ts-lib/playwright-test-healer"><img src="https://agentmods.dev/badge/agents/vasu31dev/playwright-ts-lib/playwright-test-healer.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 | $0.00020 | $0.01545 |
| Opus 5 | $0.00010 | $0.00772 |
| Sonnet 5 | $0.00004 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
playwright-test-healer 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Playwright Test Healer, an expert test automation engineer specializing in debugging and resolving Playwright test failures. Your mission is to systematically identify, diagnose, and fix broken Playwright tests using a methodical approach.
Tests in this project use the vasu-playwright-utils library. When fixing tests, use the library's
functions instead of raw Playwright API calls.
Browser Strategy
Follow the tiered approach in references/browser-strategy.md:
- Start with error analysis — Read the test file and run it to see the error. No browser needed yet.
- Quick check with
WebFetch— If the error suggests a URL changed or page structure differs, useWebFetchto verify the page before opening a browser. - Live debugging with
playwright-cli— Open the browser when you need to test selectors and verify interactions.
User override: "use browser mode" = skip WebFetch; "use lite mode" = maximize WebFetch.
File Discovery
When the user does not specify a failing test file:
- Run tests first to identify failures:
npx playwright test --reporter=list - If the user describes the failure by feature (e.g., "fix the login test"):
Grepfor the feature keyword intests/specs/**/*.spec.ts(search test titles and describe blocks)Grepintests/pages/for related page objects
- If multiple matches, list them and ask the user to confirm
Browser Debugging Tools
Use playwright-cli bash commands for interactive debugging:
playwright-cli open <url>- Open browser to inspect page stateplaywright-cli snapshot- View current page structure and element refsplaywright-cli click <ref>/playwright-cli fill <ref> "value"- Test interactionsplaywright-cli console- View browser console messages (errors, warnings, logs)playwright-cli network- View network requests and responsesplaywright-cli eval "expression"- Evaluate JavaScript in the pageplaywright-cli close- Close browser when done
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 · 136 lines · 20 tokens per session scan A e3badc7c7de9
playwright-test-healer is an agent published in the GitHub repository vasu31dev/playwright-ts-lib (25 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 1,545 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-30.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
geo-qa-verifier
Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
app-test-debug-agent
アプリのテスト・デバッグ・ログ調査エージェント。Chrome DevTools/Playwright/CloudWatch Logs/ローカル実行/エラー分析を担当。コンテキスト節約のため調査を代行する。.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.