Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitnpx agentmods add skills/ulises-jeremias/agent-toolkit/playwright-cliWrote 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/ulises-jeremias/agent-toolkit/playwright-cli)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/playwright-cli"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/playwright-cli.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.1 | $0.00067 | $0.01063 |
| Opus 5 | $0.00034 | $0.00531 |
| Sonnet 5 | $0.00013 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00106 |
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 3d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright CLI
Drive a real browser from the terminal using playwright-cli. The bundled
wrapper script runs the CLI through npx, so a global install is not required.
Treat this skill as CLI-first automation. Do NOT pivot to
@playwright/testtest files unless the user explicitly asks for them — for Playwright tests usee2e-runner.
When to use
- Quick, one-off browser automation from the shell (snapshot → interact → screenshot/trace).
- Reproducing a UI bug step-by-step with persistent sessions.
- Extracting data from a page that requires JS rendering.
- Smoke-checking a deployment without authoring a test suite.
Prerequisites
npxonPATH(provided by Node.js /voltafrombootstrap).- Optional but recommended: a global install for faster startup —
npm install -g @playwright/cli@latest. - Outbound HTTPS access to npm and to the target sites.
skills check playwright-cli validates npx is present.
Wrapper script (set once per shell)
export PWCLI="$HOME/.local/share/agent-toolkit/skills/playwright-cli/scripts/playwright_cli.sh"
alias pwcli="$PWCLI"
pwcli --help
The wrapper uses npx --yes --package @playwright/cli playwright-cli, so even
without a global install the first call will fetch the package and cache it.
If PLAYWRIGHT_CLI_SESSION is set, the wrapper passes it as --session
automatically — handy to keep separate browser contexts per project.
Quick start
pwcli open https://playwright.dev --headed
pwcli snapshot
pwcli click e15
pwcli type "Playwright"
pwcli press Enter
pwcli screenshot
Core workflow
openthe page.snapshotto get stable element refs (e.g.e3).- Interact using refs from the latest snapshot.
- Re-snapshot after navigation or significant DOM changes.
- Capture artifacts (
screenshot,pdf,tracing-start/tracing-stop) when useful.
Minimal loop:
pwcli open https://example.com
pwcli snapshot
pwcli click e3
pwcli snapshot
What ships with it
2 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.
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.
- 3d ago First seen · 155 lines · 67 tokens per session scan A ee541f4d9895
playwright-cli is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,063 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-09-04.
Other skills, from other repositories
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
skillnote-doctor
A diagnostic tool for OpenClaw agents -- checks skill registry connectivity, AGENTS.md setup, config file validity, and installed skill health. Use when your setup seems broken, skills aren't loading, or you want to audit your agent's configuration.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…