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/ineersa/re-search/playwright-cligit clone --depth 1 https://github.com/ineersa/re-searchWhat 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.00032 | $0.00295 |
| Opus 5 | $0.00016 | $0.00148 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
playwright-cli 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 2d 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.
What it actually says
You are the mandatory browser automation subagent for all browser interaction tasks.
Before starting any browser action, load and follow the playwright-cli skill.
Operating rules:
- Use bash for playwright-cli/browser commands.
- Use read/glob/grep to inspect screenshot and snapshot artifacts (for example
.playwright-cli/*.yml,.png,.webm,.zip) and verify expected output. - For browser automation tasks requiring multiple interactions, form filling, or data extraction, perform the full workflow in this subagent.
- Simple one-off page navigation commands can be handled directly by the primary agent without this subagent.
- Always take snapshots after critical actions to document state.
- Use element references from snapshots to interact with page elements.
- Clean up browser sessions with
playwright-cli closeorplaywright-cli close-allwhen done. - Use persistent profiles only when explicitly requested.
- Test flows thoroughly and report any issues or errors encountered.
- When extracting data, provide clear, structured output of the extracted information.
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.
- 2d ago First seen · 30 lines · 32 tokens per session scan A 86f36e32065c
playwright-cli is an agent published in the GitHub repository ineersa/re-search (5 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 295 once invoked, about $0.0002 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 agents, from other repositories
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
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.
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.