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 Vironnimo/vbot --skill playwright-cligit clone --depth 1 https://github.com/Vironnimo/vbotWrote 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/vironnimo/vbot/playwright-cli)<a href="https://agentmods.dev/skills/vironnimo/vbot/playwright-cli"><img src="https://agentmods.dev/badge/skills/vironnimo/vbot/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/vironnimo/vbot/playwright-cli"><img src="https://agentmods.dev/badge/skills/vironnimo/vbot/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.00019 | $0.03363 |
| Opus 5.5 | $0.00008 | $0.01345 |
| Sonnet 5.5 | $0.00004 | $0.00673 |
| Haiku 4.5 | $0.00002 | $0.00336 |
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 17d 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with playwright-cli
Using this Skill in vBot
Run CLI commands through the shell Tool on the server host. Check playwright-cli --version; these instructions accompany @playwright/cli 0.1.19. If the CLI is missing or older, follow Installation below. Node.js 18 or newer and npm are required for installation. A missing browser executable requires the browser installation command reported by the CLI. Headed windows and the annotation dashboard appear on the server host; use headless operation when that host has no graphical display.
Choose a unique browser session name for the current task and pass -s=<name> on every browser command, including the examples below. Reuse that name across calls. Close only your named session when finished; detach from browsers you attached to. Use close-all, kill-all, or profile deletion only when the user's task explicitly covers those other sessions or data.
Read linked reference files on demand with skill(name="playwright-cli", file_path="references/..."). When the references run a command in the background, run it with run_in_background true and look for the line they wait for with background_tasks action status; stop the command with action stop. CLI output may link to snapshots, logs, screenshots, or traces saved on the server: read the relevant files with the available file Tools. A printed file path alone does not show its contents. Keep the working directory consistent across calls. Use current snapshot refs or verified locators, inspect the resulting page before repeating an uncertain action, and verify the requested outcome.
Quick start
# open new browser
playwright-cli open
# navigate to a page
playwright-cli goto https://playwright.dev
# interact with the page using refs from the snapshot
playwright-cli click e15
playwright-cli type "page.click"
playwright-cli press Enter
# take a screenshot (rarely used, as snapshot is more common)
playwright-cli screenshot
# close the browser
playwright-cli close
What ships with it
11 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.
- LICENSE 11 KB
- references/element-attributes.md 665 B
- references/playwright-tests.md 1.7 KB
- references/request-mocking.md 2.1 KB
- references/running-code.md 5.5 KB
- references/session-management.md 5.5 KB
- references/storage-state.md 5.1 KB
- references/test-generation.md 16 KB
- references/tracing.md 3.4 KB
- references/video-recording.md 5.3 KB
- UPSTREAM.json 1.3 KB
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.
- 17d ago Changed 4ef32edc3001
- 1mo ago Changed 458baea00541
- 1mo ago First seen · 434 lines · 19 tokens per session scan A ea3bdfb3933d
playwright-cli is a skill published in the GitHub repository Vironnimo/vbot (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 3,363 once invoked, about $0.0001 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-09-11.
Other skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.