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 skills add IvanCampos/agents --skill playwright-cligit clone --depth 1 https://github.com/IvanCampos/agentsWrote 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/ivancampos/agents/playwright-cli)<a href="https://agentmods.dev/skills/ivancampos/agents/playwright-cli"><img src="https://agentmods.dev/badge/skills/ivancampos/agents/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/ivancampos/agents/playwright-cli"><img src="https://agentmods.dev/badge/skills/ivancampos/agents/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.00074 | $0.01103 |
| Opus 5.5 | $0.00030 | $0.00441 |
| Sonnet 5.5 | $0.00015 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00110 |
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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright CLI
Use playwright-cli directly (already installed) to execute browser automation from natural-language requests.
Quick Start
- Verify the CLI is available:
command -v playwright-cli >/dev/null 2>&1 - Open a browser session:
playwright-cli open https://example.com - Capture refs before ref-based commands:
playwright-cli snapshot
Natural-Language Execution Workflow
- Parse the request into atomic actions.
- Convert each action to command templates from
references/command-map.md. - Run
playwright-cli snapshotbefore commands that require element refs (click,fill,check,select,hover,drag, etc.) unless a fresh snapshot is already available. - Re-run
playwright-cli snapshotafter navigation or major DOM changes. - For assertions, prefer
playwright-cli evaland parse the### Resultvalue from stdout. - Treat
### Erroroutput as command failure, even when process exit code is0. - For screenshots, capture PNG first, then compress to JPEG with
ffmpegbefore final save/return. - Use explicit filenames when saving artifacts (screenshots, snapshots, PDFs, videos, storage state).
- Return executed commands and key results (URLs, counts, file paths, errors).
Command Mapping Rules
- Map intent verbs directly:
- open/launch ->
open - navigate ->
goto - click/tap ->
click - double click/double tap ->
dblclick - type/input ->
type - fill/set field ->
fill - back/forward/refresh ->
go-back/go-forward/reload
- open/launch ->
- Preserve user-provided optional flags and values.
- Omit optional args when unspecified.
- Use
-s=<name>when the user asks for a named/session-isolated browser. - Prefer native commands over
evalandrun-code; useevalorrun-codeonly if no first-class command exists. - Keep session names short and filesystem-safe (lowercase letters + numbers, no punctuation, target <= 12 chars) to avoid local socket path errors on macOS.
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.
- 1mo ago First seen · 111 lines · 74 tokens per session scan A cfecc4f0f13c
playwright-cli is a skill published in the GitHub repository IvanCampos/agents (5 stars, last pushed 8mo ago), licensed MIT. It adds 74 tokens to every session and 1,103 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-31.
Other skills, from other repositories
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
browser-qa
Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.
browser-qa
Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.
composio-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.
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions…
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.