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/jimezsa/opencolab/browser-usenpx skills add jimezsa/opencolab --skill browser-usegit clone --depth 1 https://github.com/jimezsa/opencolabWrote 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/jimezsa/opencolab/browser-use)<a href="https://agentmods.dev/skills/jimezsa/opencolab/browser-use"><img src="https://agentmods.dev/badge/skills/jimezsa/opencolab/browser-use.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.00055 | $0.01063 |
| Opus 5 | $0.00028 | $0.00531 |
| Sonnet 5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
browser-use
Automated browser control via the browser-use CLI. Navigate pages, fill forms, click elements, take screenshots, and extract content — all from the command line. On most installs it is backed by Playwright Chromium under the hood — but not on all of them; verify before relying on it.
⚠️ Verify the interface before trusting this doc. On some machines this CLI does not launch its own Playwright browser — it attaches over CDP to an already-running Chromium/Brave, and there is no
--profileflag. Runbrowser-use skill show(or--doctor) to confirm the real interface first. If it attaches over CDP: persistence only happens if you launch the browser with your own--user-data-diron a debug port; modern Brave/Chrome (136+) refuses remote debugging on the default profile, so use a dedicated user-data-dir and never chase thechrome://inspecttoggle.
Prerequisites
- Python 3.11+ (3.12 recommended)
- A Python virtual environment with
browser-useinstalled (pip install browser-use) - Playwright Chromium installed (
python -m playwright install chromium) - A graphical display when running headed (Linux: an X / Wayland session; macOS / Windows: native window)
Environment Setup
Every browser-use command needs the venv activated. On Linux you also need to point DISPLAY at the active session and (optionally) tell Playwright where its browsers live.
# activate the venv that has browser-use installed
source <path/to/venv>/bin/activate
# Linux only — point at the active X/Wayland display
export DISPLAY=:0 # adjust to match the running session (:0, :1, ...)
# optional — pin the Playwright browser cache location
export PLAYWRIGHT_BROWSERS_PATH="$HOME/.playwright"
macOS and Windows do not need DISPLAY; the headed flag just opens a native window.
Quick Reference
# Open a URL (headed — visible window)
browser-use --headed open <url>
# Open headless (no visible window)
browser-use open <url>
# See numbered interactive elements on current page
browser-use state
# Click element by index
browser-use click <index>
# Type into an input field by index
browser-use input <index> "text"
# Take a screenshot
browser-use screenshot output.png
# Scroll the page
browser-use scroll [up|down]
# Go back
browser-use back
# Press keys (e.g. Enter, Tab)
browser-use keys Enter
# Select from dropdown
browser-use select <index> "value"
# Extract page content
browser-use extract
# Close the browser
browser-use close
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 · 105 lines · 55 tokens per session scan A ed670733bebc
browser-use is a skill published in the GitHub repository jimezsa/opencolab (11 stars, last pushed 21d ago), licensed MIT. It adds 55 tokens to every session and 1,063 once invoked, about $0.0003 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
pixelbrowse
Screenshot and visually read any web page or document using pixelshot. Use instead of fetching raw HTML when you need to see what a page looks like, read visual content (charts, diagrams, infographics), check layouts, or verify UI. Triggers: "look at this page", "screenshot", "what does this site look like", "check…
ddgs
Use when an agent needs to search the web, find images/news/videos/books, or extract content from a URL. Covers the ddgs Python library, CLI, and MCP server integration.
ketch
Research skill for ketch — a fast stateless CLI for web search, OSS code search, curated library docs, page scraping, and site crawling; an optional MCP server exists for operators who want it, but the CLI is the primary interface. Use when a question needs live sources: 'research X', 'what are people saying about Y'…
tavily-hikari-crawl
Crawl bounded sites through Tavily Hikari with tvly-hikari.
ego-search
Skill "ego-search" from taxueseek/argo, covering ego-search(argo 子技能), 完全态架构, 探测双运行时 + 专业模式, 显式指定运行时(任一安装即可) and 同站登录态保温.
Fetch a Reddit post URL via old.reddit.com HTML scraping — the .json API is blocked for unauthenticated requests since May 2026. Returns structured data: post metadata + nested comments (with depth) + unique external links categorized (github/reddit/external). Persists into capstore tables (reddit.posts, .comments…