Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add freema/cursor-plugin-cc/plugin install cursorWrote 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/commands/freema/cursor-plugin-cc/browser)<a href="https://agentmods.dev/commands/freema/cursor-plugin-cc/browser"><img src="https://agentmods.dev/badge/commands/freema/cursor-plugin-cc/browser/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/commands/freema/cursor-plugin-cc/browser"><img src="https://agentmods.dev/badge/commands/freema/cursor-plugin-cc/browser.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.00031 | $0.00122 |
| Opus 5.5 | $0.00012 | $0.00049 |
| Sonnet 5.5 | $0.00006 | $0.00024 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
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.
What it actually says
!node "${CLAUDE_PLUGIN_ROOT}/scripts/browser.mjs" -- "$ARGUMENTS"
Present the browser report verbatim. If the preflight fails because the chrome-devtools MCP is not configured, relay the setup instructions from the error to the user — do not try to install or configure the MCP yourself.
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 · 10 lines · 31 tokens per session scan A 65068b9337e4
browser is a command published in the GitHub repository freema/cursor-plugin-cc (36 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 122 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 commands, from other repositories
web-runtime-verify
Verify a built web frontend at runtime: serve the build, assert page identity, run the web battery (overflow 320 to 2560, keyboard, console, Lighthouse, axe), and decide a PASS/FAIL/BLOCKED gate. Fixes are routed, not applied. Do not use to plan (implementation-plan), write code (implement-approved-slice), for perf…
ui-aqa-flow-selector-identification
Phase 4 Selector Identification of ui-aqa-flow.
ui-aqa-flow-selector-implementation
Phase 5 Selector Implementation of ui-aqa-flow.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
api-runtime-verify
Verify a built backend HTTP surface at runtime: per route, record the response, assert it against the slice's acceptance behavior, and decide PASS/FAIL/BLOCKED. Do not use to review a contract before implementation (use api-contract-review or graphql-contract-review), write code (use implement-approved-slice), triage…