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/clawcap/manobrowser/browser-automationnpx skills add ClawCap/ManoBrowser --skill browser-automationgit clone --depth 1 https://github.com/ClawCap/ManoBrowserWrote 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/clawcap/manobrowser/browser-automation)<a href="https://agentmods.dev/skills/clawcap/manobrowser/browser-automation"><img src="https://agentmods.dev/badge/skills/clawcap/manobrowser/browser-automation.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.00103 | $0.07324 |
| Opus 5 | $0.00051 | $0.03662 |
| Sonnet 5 | $0.00021 | $0.01465 |
| Haiku 4.5 | $0.00010 | $0.00732 |
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 4d 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 — 875 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation Skill
Complete browser automation workflow based on MCP Browser Server, providing stable and reliable web page operations.
Core Capabilities
- CDP-Powered Automation: Chrome DevTools Protocol for reliable, background operations
- Smart Navigation System: Auto-detect open tabs, avoid redundant navigation
- Advanced Element Interaction: UID-based targeting, accessibility tree analysis
- Content Extraction: HTML/text extraction, saved locally
- Network Requests: Send HTTP requests with browser cookies
- Advanced Features: File upload, script injection, history navigation
📖 Quick Start
🎯 Execution Flow
Standard Workflow (CDP-Powered, Recommended)
1. get_windows_and_tabs (Check browser state)
2. chrome_navigate(url) (Navigate to target page, background mode)
3. chrome_screenshot(tabId) (Verify loading)
4. [Optional] chrome_page_protection_enable (Protect from user interference)
5. [Optional] chrome_accessibility_snapshot (Get interactive elements with UIDs)
6. [Optional] chrome_click_element(uid) (Click using UID - most reliable)
7. chrome_get_web_content(tabId) (Extract content)
8. [Optional] chrome_page_protection_disable (Restore user control)
9. chrome_close_tabs (Clean up: close opened tabs after completion)
⚠️ User Intervention: When encountering login/CAPTCHA/complex decisions, use mcp__user_interaction_tools__ask_user_confirmation:
Example parameters:
{
"type": "user_takeover",
"message": "Detected login required. Please complete login and click confirm.",
"confirm_text": "Continue",
"cancel_text": "Cancel",
"tabId": "1625463389",
"timeout": 300
}
CDP Advantages:
- Background execution: No tab activation, faster performance
- UID-based targeting: Most reliable element location method
- Better error handling: CDP provides detailed error information
- Persistent state: Maintains page state across operations
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.
- 4d ago First seen · 875 lines · 103 tokens per session scan A 30ff8f40e151
browser-automation is a skill published in the GitHub repository ClawCap/ManoBrowser (9 stars, last pushed 4mo ago), licensed MIT. It adds 103 tokens to every session and 7,324 once invoked, about $0.0005 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-31.
Other skills, from other repositories
aipex-browser
AI-powered browser automation using the AIPex Chrome Extension via MCP bridge. Use this skill when the agent needs to control a Chrome browser — navigating pages, clicking elements, filling forms, capturing screenshots, managing tabs, or downloading content — by connecting to the AIPex MCP bridge.
just-scrape
Search, scrape, crawl, extract structured data, and monitor web pages via the ScrapeGraph AI CLI. Use when the user asks to search the web, scrape a webpage, grab content from a URL, extract JSON from a site, crawl documentation or site sections, monitor a page for changes, inspect request history, check ScrapeGraph…
browser-relay
Control the Chrome the user already has open and logged in through the Browser Relay CLI, without launching a separate automation browser or taking over the foreground tab. Use when an agent needs to work with existing sessions, cookies, extensions, SSO or intranet pages, or a browser on another machine. Prefer the…
owb
Open Web Bridge (OWB) — drive the user's own real browser with the owb command. Read pages behind their existing logins, gather and cross-check information, fill forms, walk multi-step flows, debug their site, audit responsive/accessibility behavior, and capture or reverse-engineer network traffic. Use this whenever…
website-explorer
Discover website capabilities from user behaviors. Learn APIs and automate workflows.
codex-browser
Control Chrome via Codex Desktop's browser bridge. 52 MCP tools for tabs, navigation, DOM, input, CDP, network, file upload, dialog handling, and diagnostics.