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/ed3dai/ed3d-plugins/playwright-explorergit clone --depth 1 https://github.com/ed3dai/ed3d-pluginsWrote 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/ed3dai/ed3d-plugins/playwright-explorer)<a href="https://agentmods.dev/agents/ed3dai/ed3d-plugins/playwright-explorer"><img src="https://agentmods.dev/badge/agents/ed3dai/ed3d-plugins/playwright-explorer.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.00055 | $0.04498 |
| Opus 5 | $0.00028 | $0.02249 |
| Sonnet 5 | $0.00011 | $0.00900 |
| Haiku 4.5 | $0.00006 | $0.00450 |
Grade A, and why
playwright-explorer 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 566 lines · 55 tokens per session scan A 5aff8d8d6355
playwright-explorer is an agent published in the GitHub repository ed3dai/ed3d-plugins (248 stars, last pushed 2mo ago), with no licence file. It adds 55 tokens to every session and 4,498 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-09-03.
Other agents, from other repositories
visual-qa
Read-only. Browser-based QA via whichever backend capability detection found -- the project's existing Playwright setup, or a connected browser-automation MCP server (Chrome DevTools MCP or a generic Playwright MCP server) when Playwright isn't available at the project level. Runs existing Playwright tests (or drives…
dev-agent-visual-qa
Read-only. Browser-based QA using the project's existing Playwright setup -- runs existing Playwright tests, inspects screenshots/console/network evidence, checks functional flows, visual layout, responsive breakpoints, UX states, and basic accessibility. Only invoked when Playwright is genuinely available in the…
qa-engineer
Automated testing, E2E validation, and bug reproduction.
chrome-verify
Verifies a chrome-extension/ change before it is reported done. Checks Service Worker (Manifest v3) compatibility with vm.createContext, manifest-permissions integrity, content-script DOM contract per target site, and message-passing between popup ↔ service worker ↔ content script. Use after any change in…
browser-controller
Headless browser control via Playwright for QA testing, screenshots, form interaction, page snapshots, and accessibility auditing. The eyes of ProductionOS.
frontend-verifier
Verifies frontend via browser automation — forms, interactions, visual regressions, responsive layouts. Also fixes issues found. General frontend QA when there's no Figma involved. Only non-Figma design agent. Good for catching functional bugs (broken forms, console errors) alongside visual issues.