Borrowing it
Nothing to install: this file belongs to DynamoDS/DynamoHome. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DynamoDS/DynamoHome/master/.claude/skills/playwright-cli/SKILL.mdgit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWrote 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/dynamods/dynamohome/playwright-cli)<a href="https://agentmods.dev/skills/dynamods/dynamohome/playwright-cli"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/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.
<a href="https://agentmods.dev/skills/dynamods/dynamohome/playwright-cli"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/playwright-cli.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.00052 | $0.00532 |
| Opus 5.5 | $0.00021 | $0.00213 |
| Sonnet 5.5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
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 2mo 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 — 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:
- Add any missing
data-testidattributes to the source components (via thefrontend-agent) - Create Page Object classes in
tests/e2e/pages/ortests/e2e/components/ - Write formal test cases in the appropriate
tests/e2e/*.spec.tsfile
Do not leave raw playwright-cli findings as permanent tests — convert them into the POM structure defined in the end-to-end-testing skill.
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.
- 2mo ago First seen · 59 lines · 52 tokens per session scan A 229f21cae302
playwright-cli is a skill published in the GitHub repository DynamoDS/DynamoHome (3 stars, last pushed 11d ago), licensed MIT. It adds 52 tokens to every session and 532 once invoked, about $0.0002 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-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…