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 skills/melodic-software/claude-code-plugins/playwrightnpx skills add melodic-software/claude-code-plugins --skill playwrightgit clone --depth 1 https://github.com/melodic-software/claude-code-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/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.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.00114 | $0.02062 |
| Opus 5 | $0.00057 | $0.01031 |
| Sonnet 5 | $0.00023 | $0.00412 |
| Haiku 4.5 | $0.00011 | $0.00206 |
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 today.
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 — 102 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
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.5 KB
- reference/test-generation.md 5.3 KB
- reference/tracing-and-video.md 6.8 KB
- reference/windows-quirks.md 4.1 KB
- scripts/force-chrome-foreground.ps1 2.3 KB runs code
- scripts/update.sh 9.8 KB runs code
- scripts/update.test.sh 5.6 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.
- today 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 (14 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 2,062 once invoked, about $0.0006 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 skills, from other repositories
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
e2e-verify
面向 Bifrost 管理端的端到端 UI 与 API 验证工具。 适用于浏览器测试、场景回归、管理端接口验证与页面快照排查。 Use when: 端到端验证、功能验证、E2E 测试、UI 测试、浏览器测试、API 测试、接口验证.
playwright-pro
Production-grade Playwright testing skill for E2E suites, flaky test diagnosis, browser automation, migration from Cypress/Selenium, CI integration, visual checks, and regression validation.
configure-ux-testing
UX testing: Playwright E2E, axe-core a11y, visual regression. Use when setting up E2E testing, screenshot assertions, browser automation, or a11y CI workflows.
generate
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".