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/real-chromenpx skills add leeguooooo/chrome-use --skill real-chromegit 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/real-chrome)<a href="https://agentmods.dev/skills/leeguooooo/chrome-use/real-chrome"><img src="https://agentmods.dev/badge/skills/leeguooooo/chrome-use/real-chrome.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.1 | $0.00000 | $0.03532 |
| Opus 5 | $0.00000 | $0.01766 |
| Sonnet 5 | $0.00000 | $0.00706 |
| Haiku 4.5 | $0.00000 | $0.00353 |
Grade C, and why
real-chrome 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 2d 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.
curl -fsSL https://raw.githubusercontent.com/leeguooooo/chrome-use/main/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chrome-use — Real Chrome (Extension)
Drive the user's live, already-open, logged-in Chrome window through the extension-connect relay instead of a freshly launched browser.
Driving the user's real, already-open Chrome (extension)
When the task needs the user's live logged-in window (their real session, the window they're looking at — not a fresh browser), use the extension connect flow. One-time setup:
chrome-use extension install— registers the native-messaging host.- Install the chrome-use extension. Easiest (and restart-stable):
the Chrome Web Store, one-click Add to Chrome:
https://chromewebstore.google.com/detail/chrome-use/knfcmbamhjmaonkfnjhldjedeobeafmk
(Dev fallback:
chrome://extensions→ Developer mode → Load unpacked →extensions/ab-connect. Load-unpacked can be disabled on Chrome restart, so prefer the Store build for unattended setups.)
macOS: the "silent, all profiles" policy makes Chrome managed. Approving the configuration profile
extension installoffers puts Chrome in "managed by your organization" mode — which locks the "Use secure DNS" (DoH) setting (#187) and strips the extension's manual update/remove buttons (#186). Usechrome-use extension install --no-profileto never write it, orprofiles remove -identifier com.leeguoo.chrome-use.connectto undo it (Chrome then uninstalls the policy-installed extension — re-add it from the Store).
Once installed, plain chrome-use open <url> auto-connects through the
extension relay — auto_connect_cdp prefers the live relay over a raw
--remote-debugging-port, so Chrome 136+'s "Allow remote debugging?" consent
popup never fires. chrome-use extension connect is the explicit form of the
same path. Zero-confirmation, zero-token. Use --launch instead when a fresh,
isolated browser is fine.
Many Chrome profiles? See which one — and pick it. The relay binds to whichever profile's extension worker is talking to the native host. If a site comes back logged out, confirm it's the right profile before assuming the login is gone:
chrome-use browsers— lists every connected profile (email if the ext has the optionalidentitypermission, else a stable id; marks the default).chrome-use --browser <id|email> <cmd>— pins THIS session to that profile. It's sticky per session (the session's daemon binds on first connect), and each session can pick a different profile, so concurrent agents don't fight.chrome-use extension status/doctoralso report the current driving profile.A logged-out result on the wrong profile is not a missing login — run
browsers, then re-run with--browser <the right one>.Many ACCOUNTS on one site? Verify identity, don't assume it. Profile selection picks the browser;
whoami/--aspick the account (backed by the cookie-use vault, hash-compare only — no stored cookie values are read):
chrome-use whoami [site]— which vault account each site's live session is.chrome-use --as <site/acct> <cmd>— verifies BEFORE acting; on mismatch auto-applies that account's stored session and re-verifies.--as-strictfails (exit 1) instead of switching. Re-verified on every invocation — sessions drift (logouts, other agents, account choosers).
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.
- 2d ago Changed · +7 lines 3fe885a95e6e
- 5d ago First seen · 215 lines · 0 tokens per session scan C b9c95538c6b2
real-chrome is a skill published in the GitHub repository leeguooooo/chrome-use (163 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,532 tokens. 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
ultimate-playwright
Browser automation via ultimate-playwright-mcp. Use when the agent needs to control a shared Chrome browser — open tabs, navigate, click, type, fill forms, take snapshots. Handles multi-user tab group isolation so multiple sessions can share one browser without interference. Use for web browsing, scraping, form…
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.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
Browser-Use Automation
CLI tool for persistent browser automation with multi-session support, featuring Chromium/Real/Remote browser modes, cookie management, JavaScript execution, and long-running automation workflows.
real-browser-control
Connect an AI coding agent to the user's REAL Chrome via Real Browser MCP (local MCP server + Chrome extension over localhost WebSocket). Use for live UI verification, already-open tabs, existing cookies/SSO/2FA, staging admin panels, and any task where headless Playwright or a cloud agentic browser would miss the…
aginxbrowser
Browser engine for AI agents: fetch JS-rendered and Cloudflare-protected pages as clean markdown, run 5-engine aggregated web search (Baidu, Bing, Sogou, WeChat, Google), take screenshots as visual input, extract structured data from SPAs, and drive multi-step interactions (click, type, fill forms, login, paginate)…