playwright-cli

playwright-cli is a skill for Claude Code from zebbern/claude-code-guide. It costs 67 tokens per session (1,985 once invoked), scanned A, original, MIT.

A command-line tool for controlling a web browser. It can open pages, click and fill controls, take screenshots, test websites, and extract page data.

In plain words
What is it for?
Use it for web application tests, form filling, screenshots, website navigation, data extraction, login-state reuse, and browser debugging.
Why use it?
It lets you automate browser tasks without writing a separate script. Snapshots show which page elements can be used, reducing errors when interacting with a page.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it for web application tests, form filling, screenshots, website navigation, data extraction, login-state reuse, and browser debugging.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zebbern/claude-code-guide/playwright-cli
About the project

Claude Code Guide is a reference collection for configuring and using Claude Code, Anthropic’s command-line coding agent. Developers use it to learn commands, skills, agents, MCP, automation, security, integrations, and troubleshooting. Its catalogue add-ons provide many of the documented skills and agents.

zebbern/claude-code-guide · 4,664 stars · on GitHub

Install

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.

Any agent
npx skills add zebbern/claude-code-guide --skill playwright-cli
Clone the repo
git clone --depth 1 https://github.com/zebbern/claude-code-guide

Made for: Claude Code.

Wrote 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.

agentmods badge for playwright-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/zebbern/claude-code-guide/playwright-cli/github.svg)](https://agentmods.dev/skills/zebbern/claude-code-guide/playwright-cli)
Your own site
<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/playwright-cli"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/playwright-cli/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.

agentmods 80×15 button for playwright-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/playwright-cli"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/playwright-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,985 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Memory Poisoning · line 60
    Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
    Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
  • medium Rogue Agent · line 127
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.01985
Opus 5.5 $0.00027 $0.00794
Sonnet 5.5 $0.00013 $0.00397
Haiku 4.5 $0.00007 $0.00198

Measured 1mo ago against content hash d9d361b10171, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/playwright/playwright-cli/SKILL.md · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Browser Automation with playwright-cli

Comprehensive CLI-driven browser automation — navigate, interact, mock, debug, record, and generate tests without writing a single script file.

Quick Start

# Install and set up
playwright-cli install --skills
playwright-cli install-browser

# Open a browser and navigate
playwright-cli open https://playwright.dev

# Take a snapshot to see interactive elements (refs like e1, e2, e3...)
playwright-cli snapshot

# Interact using element refs from the snapshot
playwright-cli click e15
playwright-cli fill e5 "search query"
playwright-cli press Enter

# Take a screenshot
playwright-cli screenshot

# Close the browser
playwright-cli close

Golden Rules

  1. Always snapshot first — identify element refs before interacting; never guess ref numbers
  2. Use fill for inputs, click for buttons — type sends keystrokes one-by-one, fill replaces the entire value
  3. Named sessions for parallel work — -s=name isolates cookies, storage, and tabs per session
  4. Save auth state — state-save auth.json after login, state-load auth.json to skip login next time
  5. Trace before debugging — tracing-start before the failing step, not after
  6. run-code for advanced scenarios — when CLI commands aren't enough, drop into full Playwright API
  7. Clean up sessions — close or close-all when done; kill-all for zombie processes
  8. Descriptive filenames — screenshot --filename=checkout-step3.png not screenshot
  9. Mock external APIs only — use route to intercept third-party services, not your own app
  10. Persistent profiles for stateful flows — --persistent keeps cookies and storage across restarts

Command Reference

Core Interaction

playwright-cli open [url]                    # Launch browser, optionally navigate
playwright-cli goto <url>                    # Navigate to URL
playwright-cli snapshot                      # Show page elements with refs
playwright-cli snapshot --filename=snap.yaml # Save snapshot to file
playwright-cli click <ref>                   # Click an element
playwright-cli dblclick <ref>                # Double-click
playwright-cli fill <ref> "value"            # Clear and fill input
playwright-cli type "text"                   # Type keystroke by keystroke
playwright-cli select <ref> "option-value"   # Select dropdown option
playwright-cli check <ref>                   # Check a checkbox
playwright-cli uncheck <ref>                 # Uncheck a checkbox
playwright-cli hover <ref>                   # Hover over element
playwright-cli drag <src-ref> <dst-ref>      # Drag and drop
playwright-cli upload <ref> ./file.pdf       # Upload a file
playwright-cli eval "document.title"         # Evaluate JS expression
playwright-cli eval "el => el.textContent" <ref>  # Evaluate on element
playwright-cli close                         # Close the browser

Read the full file on GitHub · 210 lines

Files

What ships with it

10 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.

Changes

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.

  1. 1mo ago First seen · 210 lines · 67 tokens per session scan A d9d361b10171

Subscribe to this mod's changes

playwright-cli is a skill published in the GitHub repository zebbern/claude-code-guide (4,664 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,985 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories