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 leeguooooo/chrome-use --skill reactgit 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/react)<a href="https://agentmods.dev/skills/leeguooooo/chrome-use/react"><img src="https://agentmods.dev/badge/skills/leeguooooo/chrome-use/react/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/leeguooooo/chrome-use/react"><img src="https://agentmods.dev/badge/skills/leeguooooo/chrome-use/react.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.00076 | $0.00378 |
| Opus 5.5 | $0.00030 | $0.00151 |
| Sonnet 5.5 | $0.00015 | $0.00076 |
| Haiku 4.5 | $0.00008 | $0.00038 |
Grade A, and why
react 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 5d 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.
What it actually says
chrome-use — React / Web Vitals
Inspect React apps and measure Web Vitals with chrome-use's built-in react … and vitals commands.
React / Web Vitals (built-in, any React app)
chrome-use ships with first-class React introspection. Works on any
React app — Next.js, Remix, Vite+React, CRA, TanStack Start, React Native
Web, etc. The react … commands require the React DevTools hook to be
installed at launch via --enable react-devtools:
chrome-use open --enable react-devtools http://localhost:3000
chrome-use react tree # component tree
chrome-use react inspect <fiberId> # props, hooks, state, source
chrome-use react renders start # begin re-render recording
chrome-use react renders stop # print render profile
chrome-use react suspense [--only-dynamic] # Suspense boundaries + classifier
chrome-use vitals [url] # LCP/CLS/TTFB/FCP/INP + hydration
chrome-use pushstate <url> # SPA navigation (auto-detects Next router)
Without --enable react-devtools, the react … commands error. vitals
and pushstate work on any site regardless of framework.
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.
- 5d ago Changed b0edfdf15378
- 1mo ago First seen · 31 lines · 76 tokens per session scan A 93ab34d7738a
react is a skill published in the GitHub repository leeguooooo/chrome-use (202 stars, last pushed yesterday), licensed Apache-2.0. It adds 76 tokens to every session and 378 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. 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.
deep-x-research
Deep, exhaustive research on a topic across X (Twitter) by driving Grok (x.com/i/grok) through surf. Use when the user wants comprehensive X research on a concept, technique, trend, tool, or creator scene; needs categorized findings with every claim traceable to post URLs; or when a single Grok query is not enough.
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.
cursor-browser
Drive Cursor IDE's built-in Browser Tab via cursor-browser-cli. Navigate, ref snapshots, click/type/fill/scroll/select-option by ref, wait-for, lock, screenshot, console/network/inspect. For Grok Build, Claude Code, Codex in Cursor terminal. Triggers: Cursor browser, Browser Tab, /cursor-browser, snapshot, under the…
wbrowser
Use when a task needs a browser that is already signed in — reading a dashboard, checking a web app, filling a form, taking a screenshot of a real page, or debugging a site's console. Drives a real Chrome window the user signed into by hand, so no re-login and no API keys. Do not guess selectors; run wb read first and…