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 bcharleson/cursor-browser-cli --skill skillgit clone --depth 1 https://github.com/bcharleson/cursor-browser-cliWrote 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/bcharleson/cursor-browser-cli/skill)<a href="https://agentmods.dev/skills/bcharleson/cursor-browser-cli/skill"><img src="https://agentmods.dev/badge/skills/bcharleson/cursor-browser-cli/skill/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/bcharleson/cursor-browser-cli/skill"><img src="https://agentmods.dev/badge/skills/bcharleson/cursor-browser-cli/skill.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.00083 | $0.01646 |
| Opus 5.5 | $0.00033 | $0.00658 |
| Sonnet 5.5 | $0.00017 | $0.00329 |
| Haiku 4.5 | $0.00008 | $0.00165 |
Grade A, and why
cursor-browser 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cursor-browser-cli
Control Cursor’s Browser Tab in the matching project window.
This skill is only for the in-IDE Browser Tab. It does not drive an external desktop browser product. Other browser tools (if installed on the machine) are separate and independent — use those when you need a full browser profile, existing cookie sessions, or non-Cursor windows. Prefer this tool for day-to-day app UI work inside Cursor (local servers, fast ref loops, same tab as the IDE).
Install via npm install -g cursor-browser-cli, or clone this repo and run npm install.
Always pin the project first (required multi-window)
Each Cursor project has its own bridge on its own port. Never open a tab until you know which project/port you are targeting.
# 1) What bridges are live? (project → port)
cursor-browser windows
# 2) What project is THIS cwd / workspace?
cursor-browser pin
# or:
cursor-browser --workspace <project-folder> pin
# 3) Pin for the rest of the shell session
eval $(cursor-browser pin --export)
# sets CURSOR_BROWSER_WORKSPACE + CURSOR_BROWSER_CLI_PORT
Or pass every time:
cursor-browser --workspace <project-folder> whoami
cursor-browser --workspace <project-folder> open http://localhost:3000
Prefer --workspace <name> over raw port. Ports can change after
recover / Restart Server; the project name stays stable.
Multi-project days: always pass --workspace (or pin via eval $(… pin --export)).
Agent loop (preferred)
# 0) Discover + pin (once per session / project)
cursor-browser windows
cursor-browser pin
eval $(cursor-browser pin --export)
# confirm:
cursor-browser whoami
# 1) Single tab + navigate → ref snapshot printed as text
cursor-browser open http://localhost:3000
# or
cursor-browser nav http://localhost:3000
# 2) Read refs from snapshot output (e1, e5, …)
# 3) Interact by ref
cursor-browser click e5
cursor-browser fill e3 "value"
cursor-browser type e3 "more"
cursor-browser hover e2
cursor-browser press Enter
cursor-browser scroll --y 600
cursor-browser select-option e7 "option-value"
# Optional: fresh refs after same-page interact
cursor-browser fill e3 "x" --snap
# After a navigation click, prefer wait + snapshot (most reliable)
cursor-browser click e5 --wait-nav --timeout 15000
cursor-browser snapshot
# --snap on a nav click also works (CLI falls back if needed) but is slower
# 4) Wait for state (avoid races)
cursor-browser wait --url /dashboard --timeout 15000
cursor-browser wait --text "Welcome"
cursor-browser wait --ref e12
# 5) Lock while automating (optional)
cursor-browser lock
# ... actions ...
cursor-browser unlock
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 · 176 lines · 83 tokens per session scan A 17e89bf7886c
cursor-browser is a skill published in the GitHub repository bcharleson/cursor-browser-cli (2 stars, last pushed 22d ago), licensed MIT. It adds 83 tokens to every session and 1,646 once invoked, about $0.0003 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-31.
Other skills, from other repositories
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.
core
Core chrome-use usage guide. Read this before running any chrome-use commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple…
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack…
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using chrome-use via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include…
sessions
Run multiple isolated browser sessions in parallel (each --session = own cookies/tabs/refs), recover a stranded tab by CDP targetId across sessions, --reuse-tab, and reset stuck daemons (daemon status/restart). Use for multi-user flows, parallel scraping, or when a session's tab/handle got stuck.