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/leeguooooo/chrome-use/chrome-usenpx skills add leeguooooo/chrome-use --skill chrome-usegit clone --depth 1 https://github.com/leeguooooo/chrome-useWrote 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/leeguooooo/chrome-use/chrome-use)<a href="https://agentmods.dev/skills/leeguooooo/chrome-use/chrome-use"><img src="https://agentmods.dev/badge/skills/leeguooooo/chrome-use/chrome-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.00198 | $0.00968 |
| Opus 5 | $0.00099 | $0.00484 |
| Sonnet 5 | $0.00040 | $0.00194 |
| Haiku 4.5 | $0.00020 | $0.00097 |
Grade C, and why
chrome-use scanned grade C with 2 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/leeguooooo/chrome-use/main/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
web-access, WebSearch, WebFetch, curl, and built-in browser tools. Use it to How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chrome-use
Fast browser automation CLI for AI agents. Chrome/Chromium via CDP with
accessibility-tree snapshots and compact @eN element refs.
Install / self-heal: if the chrome-use (or abs) command is missing —
e.g. a command errors with "command not found" — install it from the GitHub
Release (no npm, no token), then retry. Do NOT fall back to other browser tools:
curl -fsSL https://raw.githubusercontent.com/leeguooooo/chrome-use/main/install.sh | sh
Start here
This file is a discovery stub, not the usage guide. Before running any
chrome-use command, load the actual workflow content from the CLI:
chrome-use skills get core # start here — workflows, common patterns, troubleshooting
chrome-use skills get core --full # include full command reference and templates
The CLI serves skill content that always matches the installed version,
so instructions never go stale. The content in this stub cannot change
between releases, which is why it just points at skills get core.
Route to a specialized skill by symptom
Load a specialized guide when the task falls outside plain browser web pages. Match on the situation you're in, then run the command — the binary serves the full, version-matched content:
| What you're hitting | Run |
|---|---|
An element is clearly on screen but snapshot/find returns no @ref (canvas/WebGL/game/map) |
chrome-use skills get canvas |
| Mock an API response, rewrite request headers, block a URL, record HAR | chrome-use skills get network |
| Debug React renders/state, or measure LCP/CLS/INP | chrome-use skills get react |
| Drive the user's real, already-logged-in Chrome (reuse the session) | chrome-use skills get real-chrome |
| Parallel sessions, multiple accounts, recover a stuck tab | chrome-use skills get sessions |
| Turn manual checks into a re-runnable regression suite | chrome-use skills get test |
| Electron desktop apps (VS Code, Slack, Discord, Figma, …) | chrome-use skills get electron |
| Slack workspace automation | chrome-use skills get slack |
| Exploratory testing / QA / bug hunt | chrome-use skills get dogfood |
| chrome-use inside Vercel Sandbox microVMs | chrome-use skills get vercel-sandbox |
| AWS Bedrock AgentCore cloud browsers | chrome-use skills get agentcore |
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.
- 3d ago First seen · 80 lines · 198 tokens per session scan C 1281e7542664
chrome-use is a skill published in the GitHub repository leeguooooo/chrome-use (160 stars, last pushed yesterday), licensed Apache-2.0. It adds 198 tokens to every session and 968 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It comes from a forked repository.
Other skills, from other repositories
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
surf-codebase
Navigate and modify surf-cli codebase - Chrome extension + native host for AI browser automation. Use for surf-cli code work, architecture questions, implementing browser control/CDP/accessibility/network features.
camofox-browser
Anti-detection browser automation for AI agents. Use when the user needs stealth web browsing, undetectable scraping, fingerprint spoofing, proxy rotation, or privacy-focused browser automation. Triggers include "stealth scrape", "anti-detection", "bypass fingerprinting", "camofox", "camoufox", "undetectable browser"…
camofox-cli
CamoFox CLI — 50 commands for anti-detection browser automation from the terminal. Use when the user needs CLI reference for camofox commands, terminal-based browser control, or a quick lookup of command syntax. Triggers include "camofox command", "CLI reference", "terminal browser", or any request for camofox…
Reddit automation with CamoFox CLI — login, browse, post, comment, reply with anti-detection. Use when the user needs to automate Reddit interactions, post to subreddits, comment on threads, or browse Reddit programmatically. Triggers include "reddit", "post to reddit", "reddit comment", "reddit automation", or any…
skill
Anti-detection browser automation MCP skill for OpenClaw agents with 47 tools for navigation, interaction, observation, extraction, downloads, profiles, sessions, and stealth web search.