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 irahardianto/awesome-agv --skill browser-automationgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/browser-automation)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/browser-automation"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/browser-automation/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/irahardianto/awesome-agv/browser-automation"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/browser-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 39 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 382 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 384 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 411 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00039 | $0.05161 |
| Opus 5.5 | $0.00016 | $0.02064 |
| Sonnet 5.5 | $0.00008 | $0.01032 |
| Haiku 4.5 | $0.00004 | $0.00516 |
Grade A, and why
browser-automation 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- browser-automation — 97% identical, 35 lines differ
How it starts
The opening of the file, as written. The whole thing — 645 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation (Playwright MCP)
Tool Hierarchy
PRIMARY — MCP tools (always prefer):
mcp_playwright_browser_snapshot— read page structure, get element refsmcp_playwright_browser_navigate— go to URLmcp_playwright_browser_click— click elementmcp_playwright_browser_type— type into elementmcp_playwright_browser_fill_form— fill multiple form fieldsmcp_playwright_browser_select_option— dropdown selectionmcp_playwright_browser_hover— hover elementmcp_playwright_browser_drag— drag and dropmcp_playwright_browser_drop— drop files/data onto elementmcp_playwright_browser_press_key— keyboard inputmcp_playwright_browser_evaluate— execute JS on pagemcp_playwright_browser_wait_for— wait for text/disappearance/timemcp_playwright_browser_console_messages— read console outputmcp_playwright_browser_network_requests— list network activitymcp_playwright_browser_network_request— inspect single requestmcp_playwright_browser_file_upload— upload filesmcp_playwright_browser_handle_dialog— accept/dismiss dialogsmcp_playwright_browser_tabs— manage tabsmcp_playwright_browser_resize— change viewportmcp_playwright_browser_run_code_unsafe— arbitrary Playwright code (escape hatch)
FALLBACK — CLI via run_command (only when MCP lacks capability):
- Tracing start/stop
- Video recording
- Persistent browser profiles
- Browser installation (
npx playwright install)
NEVER mix MCP and CLI for the same session. One approach per workflow.
Snapshot-First Workflow
Every browser interaction follows this loop:
- Snapshot —
mcp_playwright_browser_snapshotto understand current state - Act — click/type/navigate using refs from snapshot
- Verify — snapshot again to confirm mutation took effect
Rules:
- ALWAYS snapshot before first interaction on a page
- Use snapshot element refs (
ref="e5") for targeting — not CSS selectors - After navigation or state mutation, snapshot again to read new state
- Use
depthparam to limit snapshot size for large pages - Use
targetparam to scope snapshot to a subtree
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 · 645 lines · 39 tokens per session scan A d3704ef6662b
browser-automation is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 12d ago), licensed MIT. It adds 39 tokens to every session and 5,161 once invoked, about $0.0002 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-30.
Other skills, from other repositories
quality-engineering-playwright-pom-generation
Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture. Use when a web scenario needs a page object that does not exist yet, or when locators drift and the page object must be rebuilt.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
uat-signoff
Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.