Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install playwrightWrote 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/melodic-software/claude-code-plugins/playwright)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/playwright"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/playwright/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/melodic-software/claude-code-plugins/playwright"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/playwright.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.00119 | $0.02136 |
| Opus 5.5 | $0.00048 | $0.00854 |
| Sonnet 5.5 | $0.00024 | $0.00427 |
| Haiku 4.5 | $0.00012 | $0.00214 |
Grade A, and why
playwright 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 28d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright CLI, live browser automation
Wraps Microsoft's @playwright/cli for token-efficient browser automation. Snapshots and screenshots write to disk; only paths come back into context, a substantial token reduction versus Playwright MCP's in-context payloads.
Requires playwright-cli on PATH (npm install -g @playwright/cli). If it is missing, tell the user to install it rather than substituting a different automation surface.
Quick start (90% of use)
playwright-cli kill-all # start clean (no stale sessions)
playwright-cli -s=<flow> open <url> # named session, headless by default
playwright-cli -s=<flow> snapshot # writes YAML with element refs (e1, e2, ...)
playwright-cli -s=<flow> click e42 # interact by ref
playwright-cli -s=<flow> fill e37 "input" --submit # fill + press Enter
playwright-cli -s=<flow> screenshot --filename=meaningful-name.png
playwright-cli -s=<flow> console # summarize console messages
playwright-cli -s=<flow> close # tear down
Read the YAML snapshot file directly to locate element refs. Do not dump it into context.
Conventions
- Always use named sessions (
-s=<flow>) for multi-step work. Default (unnamed) sessions are hard to isolate when things go sideways kill-allat the start of a fresh E2E run guards against stale daemon state from prior sessionscloseat the end. Don't leave zombie browsers--headedonly when the user explicitly wants to observe. On Windows, headed browsers spawn in the background and don't auto-focus. See reference/windows-quirks.md- Artifacts land in
.playwright-cli/relative to CWD at command time. Add.playwright-cli/to the project's.gitignoreif it isn't already. For meaningful artifacts (evidence for PRs, regression baselines), pass--filename=<descriptive>.png; let timestamp-named snapshots pile up as throwaway intermediate state - Use element refs from snapshots (
e15,e37), not CSS selectors. Snapshots use accessibility roles, which survive cosmetic UI changes - Judge visual questions from the screenshot itself. The snapshot YAML carries roles and text, not layout or color. For "does the modal cover the button" or "does the chart match the table", Read the screenshot file and answer that one specific question from the image; share the file path as evidence rather than retyping what it shows
What ships with it
27 files 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.
- actions/update.md 5.1 KB
- evals/evals.json 3.2 KB
- reference/commands.md 5.7 KB
- reference/e2e-orchestrator-recipe.md 4.1 KB
- reference/network-mocking.md 2.9 KB
- reference/running-code.md 4.7 KB
- reference/sessions.md 3.2 KB
- reference/snapshots-and-refs.md 3.4 KB
- reference/storage-and-auth.md 3.7 KB
- reference/test-generation.md 5.3 KB
- reference/tracing-and-video.md 6.7 KB
- reference/windows-quirks.md 3.7 KB
- scripts/force-chrome-foreground.ps1 2.2 KB runs code
- scripts/update.sh 9.6 KB runs code
- scripts/update.test.sh 5.5 KB runs code
- vendor/.markdownlint-cli2.jsonc 570 B
- vendor/LICENSE 11 KB
- vendor/references/element-attributes.md 665 B
- vendor/references/playwright-tests.md 1.7 KB
- vendor/references/request-mocking.md 2.1 KB
- vendor/references/running-code.md 5.5 KB
- vendor/references/session-management.md 5.5 KB
- vendor/references/storage-state.md 5.1 KB
- vendor/references/test-generation.md 16 KB
- vendor/references/tracing.md 3.4 KB
- vendor/references/video-recording.md 5.3 KB
- vendor/SKILL.md 12 KB
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.
- 28d ago Changed · +1 lines 16893cacc6ff
- 1mo ago Changed · +5 tokens per session d378dbeb3145
- 1mo ago First seen · 102 lines · 114 tokens per session scan A b91ebd18822d
playwright is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 119 tokens to every session and 2,136 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
e2e-flow-verifier
Use when verifying complete user flows end-to-end with the qe-browser skill (Vibium), recording session evidence, and asserting state at each step. For product verification with real browser automation.
webapp-selenium-testing
Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5. Use for creating, debugging, or running Selenium specs, implementing Page Objects, handling explicit waits, capturing screenshots, or setting up Maven test projects. Supports Chrome, Firefox, and Edge. Keywords: Selenium WebDriver, Java…
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.