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 pandysp/claude-plugins --skill drive-browsergit clone --depth 1 https://github.com/pandysp/claude-pluginsWrote 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/pandysp/claude-plugins/drive-browser)<a href="https://agentmods.dev/skills/pandysp/claude-plugins/drive-browser"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/drive-browser/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/pandysp/claude-plugins/drive-browser"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/drive-browser.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.00172 | $0.01144 |
| Opus 5.5 | $0.00069 | $0.00458 |
| Sonnet 5.5 | $0.00034 | $0.00229 |
| Haiku 4.5 | $0.00017 | $0.00114 |
Grade A, and why
drive-browser 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive browser with Playwright
Use Playwright for precise browser actions and for a screenshot-and-click loop. Pick how to interact by what the page exposes, not by habit.
Decide: two independent choices
How you find and act on elements:
- Locators (default).
getByRole/getByLabel/getByTextfirst: they auto-wait and re-resolve as the page changes. Use CSS only when a locator can't express the target. This handles your own app and most real sites. - Vision: only when the structure is genuinely opaque (custom canvas, a widget locators can't reach): screenshot → read it → click coordinates.
Where the page runs:
- Clean state or another login: create a new browser context, either in an attached browser or in a fresh launch. Never clear the user's context to get a clean one.
- The user's existing login: attach to the real browser and use its existing context. Read Safety first; open a task-owned tab rather than taking over an existing one unless asked.
These choices are independent: locators work with an existing login, and vision works in a fresh context. See setup and lifecycle recipes for connection, launch, and cleanup. For multi-step exploration, keep the browser and page handles in the host's persistent Node REPL rather than reconnecting for each action.
Locator mode
Prefer page.getByRole('button', { name: 'Save' }) and getByLabel('Email').
Use page.locator(css) only when needed, and page.evaluate(fn) for DOM reads
that locators don't express. Wait for the state you need (locator.waitFor(),
page.waitForURL(), page.waitForFunction()), not a guessed delay. For CSS-media
features, use page.emulateMedia({ reducedMotion: 'reduce' }).
Vision mode
Work one step at a time: screenshot → read the PNG → choose coordinates →
page.mouse.click(x, y) → screenshot again. Don't write a blind script with
guessed coordinates.
Take viewport screenshots with page.screenshot({ path: 'step.png', scale: 'css' }).
Each image pixel then matches a CSS pixel, so use the image coordinates directly
in page.mouse.click. Read the image at its original dimensions; a resized
preview changes the coordinates. Re-screenshot after anything that moves controls.
What ships with it
1 file 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 Changed · -34 lines e849989b3197
- 1mo ago First seen · 120 lines · 172 tokens per session scan A 1de4109b4d3b
drive-browser is a skill published in the GitHub repository pandysp/claude-plugins (6 stars, last pushed 7d ago), licensed MIT. It adds 172 tokens to every session and 1,144 once invoked, about $0.0007 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
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…
interactive-login
Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.
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.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
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.
open-design-browser
Inspect and exercise local HTML design artifacts and library prototype previews with the existing agent-browser CLI, including screenshots, interaction checks, and rendered DOM snapshots. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser…