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 agentmods add skills/vladolaru/claude-code-plugins/browser-interactionnpx skills add vladolaru/claude-code-plugins --skill browser-interactiongit clone --depth 1 https://github.com/vladolaru/claude-code-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/vladolaru/claude-code-plugins/browser-interaction)<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/browser-interaction"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/browser-interaction.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 | $0.00035 | $0.02783 |
| Opus 5 | $0.00017 | $0.01392 |
| Sonnet 5 | $0.00007 | $0.00557 |
| Haiku 4.5 | $0.00003 | $0.00278 |
Grade A, and why
browser-interaction 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 yesterday.
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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Interaction
Browser automation via MCP tools (chrome-devtools or playwright).
Prerequisites
Load browser MCP tools before any interaction:
ToolSearch query: "+chrome-devtools list pages snapshot navigate screenshot"
If chrome-devtools unavailable, fall back to playwright:
ToolSearch query: "+playwright browser snapshot navigate"
Tool Mapping
| Action | Chrome DevTools | Playwright |
|---|---|---|
| List pages | list_pages |
browser_tabs |
| Navigate | navigate_page |
browser_navigate |
| Click | click |
browser_click |
| Fill | fill |
browser_type |
| Screenshot | take_screenshot |
browser_take_screenshot |
| Snapshot | take_snapshot |
browser_snapshot |
| Wait | wait_for |
browser_wait_for |
RULE 0: Fresh Snapshot Before Interaction
Every browser interaction follows this loop:
Navigate → Fresh Snapshot → Interact (using uid) → Verify
↑ │
└────────────────────────────────────────┘
Element refs (uid="1_5") regenerate per snapshot. Old refs match DIFFERENT elements after navigation.
# WRONG: uid reused after navigation
take_snapshot() # uid="1_42" → Save button
navigate_page(url="/foo")
click(uid="1_42") # uid "1_42" may now match an unrelated element
# RIGHT: fresh snapshot after every navigation
navigate_page(url="/foo")
take_snapshot() # fresh uids
click(uid=<new>)
Navigate:
mcp__chrome-devtools__navigate_page(type: "url", url: "http://localhost:8080/wp-admin/", timeout: 30000)
Snapshot → Interact:
mcp__chrome-devtools__take_snapshot()
mcp__chrome-devtools__click(uid: "1_42", includeSnapshot: true)
mcp__chrome-devtools__fill(uid: "1_15", value: "[email protected]")
Verify (see RULE 1 for screenshot selection):
mcp__chrome-devtools__take_screenshot(uid: "3_272")
RULE 1: Token-Efficient Interaction
Choose the cheapest tool for your goal:
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.
- yesterday First seen · 275 lines · 35 tokens per session scan A 2e2ae3141617
browser-interaction is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,783 once invoked, about $0.0002 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-03.
Other skills, from other repositories
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
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-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction using playwright-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.