playwright-cli

A command-line browser automation tool for navigating web pages, clicking controls, filling forms, taking screenshots, and reading page data.

In plain words
What is it for?
Use it to explore a local development server, inspect page elements, perform user actions, run small JavaScript checks, view console output, and capture screenshots.
Why use it?
It helps test how a web application behaves in a real browser and exposes missing selectors or interaction problems before formal tests are written.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/dynamods/dynamohome/playwright-cli
Any agent
npx skills add DynamoDS/DynamoHome --skill playwright-cli
Clone the repo
git clone --depth 1 https://github.com/DynamoDS/DynamoHome

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 532 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.00532
Opus 5 $0.00026 $0.00266
Sonnet 5 $0.00010 $0.00106
Haiku 4.5 $0.00005 $0.00053

Measured yesterday against content hash 229f21cae302, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

.claude/skills/playwright-cli/SKILL.md · 59 lines

How it starts

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

Browser Automation with playwright-cli

Used in DynamoHome for exploratory testing — navigating the live dev server, discovering data-testid gaps, and validating interactions before writing formal Playwright tests.

Typical DynamoHome workflow

# 1. Start the dev server first
npm run start

# 2. Open the app
playwright-cli open http://localhost:8080

# 3. Take a snapshot to see the current state and element refs
playwright-cli snapshot

# 4. Interact with elements using refs from the snapshot
playwright-cli click e5
playwright-cli snapshot

# 5. Close when done
playwright-cli close

Core commands

playwright-cli open http://localhost:8080   # open the app
playwright-cli goto http://localhost:8080   # navigate to a URL
playwright-cli snapshot                     # capture page state + element refs
playwright-cli click e3                     # click element by ref
playwright-cli hover e4                     # hover over element
playwright-cli press Enter                  # keyboard press
playwright-cli eval "document.title"        # run JS on the page
playwright-cli screenshot                   # take a screenshot
playwright-cli console                      # view console output
playwright-cli network                      # view network requests
playwright-cli close                        # close the browser

Snapshots

After each command, playwright-cli returns a snapshot of the current page with element refs (e.g. e5, e12). Use these refs to interact with specific elements. Snapshots are saved under .playwright-cli/ — this folder is git-ignored.

What to do with findings

Once you have identified the interactions and selectors needed:

  1. Add any missing data-testid attributes to the source components (via the frontend-agent)
  2. Create Page Object classes in tests/e2e/pages/ or tests/e2e/components/
  3. Write formal test cases in the appropriate tests/e2e/*.spec.ts file

Do not leave raw playwright-cli findings as permanent tests — convert them into the POM structure defined in the end-to-end-testing skill.

Read the full file on GitHub · 59 lines

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. yesterday First seen · 59 lines · 52 tokens per session scan A 229f21cae302

Subscribe to this mod's changes

playwright-cli is a skill published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It adds 52 tokens to every session and 532 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-08-31.

Related

Other skills, from other repositories

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…

heygen-com/hyperframes · 92 tokens

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

mintlify-preview

Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".

latitude-dev/latitude-llm · 69 tokens