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 vibesurf-ai/claude-surf --skill browser-usegit clone --depth 1 https://github.com/vibesurf-ai/claude-surfWrote 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/vibesurf-ai/claude-surf/browser-use)<a href="https://agentmods.dev/skills/vibesurf-ai/claude-surf/browser-use"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/browser-use/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/vibesurf-ai/claude-surf/browser-use"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/browser-use.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.00035 | $0.00954 |
| Opus 5 | $0.00017 | $0.00477 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
browser-use 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 10d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser-Use Agent - Autonomous Automation
Overview
Launch AI sub-agents that complete multi-step browser tasks autonomously. Most powerful VibeSurf capability.
When to Use
browser-use is a high-level, task-oriented sub-agent approach:
- Complex tasks where you describe the goal and desired output, let the agent figure out the steps
- Long workflows that would require many manual browser operations
- Unknown or dynamic UI that needs autonomous exploration
- Parallel automation across multiple tabs
Note: browser-use and browser skill are complementary, not mutually exclusive. Both can accomplish the same tasks - browser-use is higher-level automation, while browser gives you precise control.
Available Actions
| Action | Description |
|---|---|
execute_browser_use_agent |
Execute browser-use agent tasks. Specify tab_id to work on specific tab. Each tab_id must be unique during parallel execution. |
How It Works
Describe the goal, agent figures out the steps:
- Navigate to URLs
- Find and interact with elements
- Fill forms
- Extract data
- Return structured results
Task-Oriented Thinking
Good task descriptions:
- ✅ "Fill out the registration form with these details"
- ✅ "Search for Python tutorials and summarize top 3"
- ✅ "Go to login page, authenticate, then check dashboard"
Bad task descriptions:
- ❌ "Click button" (too vague, use
browser) - ❌ "Extract prices" (use
js_codeinstead) - ❌ "Step 1: navigate, Step 2: click..." (let agent figure it out)
Working with Existing Tabs
🎯 Important: tab_id Selection
When user refers to their already-opened pages (e.g., "the current page", "from my open tabs", "the second tab"):
- FIRST call
get_browser_stateto get all open tabs and their IDs- THEN use the correct
tab_idfrom the response- NEVER use
tab_id: nullor omit it - that creates a NEW tabKey distinction:
tab_id: "existing_id"→ Work on user's existing tabtab_id: nullor omitted → Create a brand new tab
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.
- 10d ago First seen · 108 lines · 35 tokens per session scan A 2da2320af634
browser-use is a skill published in the GitHub repository vibesurf-ai/claude-surf (24 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 954 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-08-30.
Other skills, from other repositories
moai-platform-chrome-extension
Chrome Extension Manifest V3 development specialist covering service workers, content scripts, message passing, chrome. APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing. Use when building browser extensions.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
browser-tools
Security wrapper over the upstream agent-browser skill, adding URL blocklisting, rate limiting, robots.txt enforcement, and scraping guardrails. Use when automating browser workflows that need safety limits.
browser-automation-agent
Automate web browsers for AI agents using agent-browser CLI with deterministic element selection.
using-web-scraping
Search and scrape public web content with headless Chrome and DuckDuckGo using safe practices.
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.