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 iFurySt/open-browser-use --skill chromegit clone --depth 1 https://github.com/iFurySt/open-browser-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/ifuryst/open-browser-use/chrome)<a href="https://agentmods.dev/skills/ifuryst/open-browser-use/chrome"><img src="https://agentmods.dev/badge/skills/ifuryst/open-browser-use/chrome/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/ifuryst/open-browser-use/chrome"><img src="https://agentmods.dev/badge/skills/ifuryst/open-browser-use/chrome.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 666 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00034 | $0.13431 |
| Opus 5.5 | $0.00014 | $0.05372 |
| Sonnet 5.5 | $0.00007 | $0.02686 |
| Haiku 4.5 | $0.00003 | $0.01343 |
Grade A, and why
Chrome 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 1mo 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 — 1,130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome
Use this skill when the user mentions @chrome.
Chrome is the routing touchpoint for the Codex Chrome Extension:
- Use Chrome directly for browser automation requests and for Chrome setup, detection, repair, or profile checks.
- For bare or general
@chromerequests, do not ask a clarification question just because the request is ambiguous. Proceed with browser automation in this skill using thechromebackend. - If communication with the Codex Chrome Extension ultimately fails, even after checks, do not attempt to complete the user's request using applescript, bash commands or any other scripting methods.
- Do not install or repair the native host yourself. If native host setup appears broken, tell the user to reinstall the Chrome plugin from the Codex plugin UI.
Before using this skill for the first time in the current conversation context, read the entire SKILL.md file in one read. Do not use a partial range such as sed -n '1,220p'; read through the end of the file. Do not mention this internal skill-loading step to the user.
Chrome Extension Checks
On the first Chrome-backed browser task in a session, try a lightweight browser-client call such as listing open tabs after bootstrap. If the call fails, wait 2 seconds and retry the same lightweight browser-client call once. Any non-error response means the extension is installed and working.
If browser-client still reports that it cannot communicate with Chrome after that retry, confirm that Chrome is installed, running and that the extension is present in the selected Chrome profile:
From the plugin root, use node_repl to run:
scripts/chrome-is-running.js --check
scripts/installed-browsers.js --check
scripts/check-extension-installed.js --json
scripts/check-native-host-manifest.js --json
Depending on the outcome follow the following checks. Be sure to ask the user permission when required, if it is stated in the check.
1. Chrome is not installed
Keep the first response short and non-technical unless the user asks for more information.
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.
- 1mo ago First seen · 1,130 lines · 34 tokens per session scan A fe3b19bef0ec
Chrome is a skill published in the GitHub repository iFurySt/open-browser-use (379 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 13,431 once invoked, about $0.0001 per session on Opus 5.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
tidesurf-browser
Drive a real Chromium browser through the tidesurf CLI or MCP tools. Use when a task needs live web browsing: reading pages as compact, token-efficient text with action IDs; clicking, typing, selecting, and scrolling elements by ID; taking screenshots of the full page, viewport, or one element; managing tabs; handling…
browser_harness
../../SKILL.md.
browser-use-terminal
Direct browser control via the Browser Use Terminal CLI. Use when the user wants to automate, scrape, test, or interact with web pages — you drive the browser yourself with Python helpers.
browser-harness
Control a real browser via CDP: clicking, typing, navigation, logged-in sessions, JS-rendered or bot-protected pages. Not for plain HTTP fetches of public content - use curl for those.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…