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.
git clone --depth 1 https://github.com/unbrowse-ai/unbrowseWrote 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/rules/unbrowse-ai/unbrowse/unbrowse-web)<a href="https://agentmods.dev/rules/unbrowse-ai/unbrowse/unbrowse-web"><img src="https://agentmods.dev/badge/rules/unbrowse-ai/unbrowse/unbrowse-web/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/rules/unbrowse-ai/unbrowse/unbrowse-web"><img src="https://agentmods.dev/badge/rules/unbrowse-ai/unbrowse/unbrowse-web.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.00215 | $0.00215 |
| Opus 5.5 | $0.00086 | $0.00086 |
| Sonnet 5.5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
unbrowse-web 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
For any task that needs a website (reading a page, looking something up on a site, filling or submitting something on a site), use the Unbrowse MCP tools rather than a local browser or raw HTTP:
unbrowse_scrape {url}reads a page as clean markdown (renders JavaScript, reuses saved logins).unbrowse_discover {query}thenunbrowse_run {capability, input}performs a task through a learned site API.input_requiredmeans answer withunbrowse_resumeon the same run.unbrowse_browse_open/_act/_finishdrive the cloud browser when nothing matches; finishing teaches Unbrowse the route so the next call needs no browser.
Local pages (localhost, 127.0.0.1) are fine to open locally for app testing. Follow the unbrowse skill for sign-in, verification and write-authorization rules.
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 d51b2be3d471
- 17d ago First seen · 13 lines · 215 tokens per session scan A 726c66d3e0e0
unbrowse-web is a cursor rule published in the GitHub repository unbrowse-ai/unbrowse (794 stars, last pushed yesterday), licensed MIT. It adds 215 tokens to every session, about $0.0009 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-09-29.
Other cursor rules, from other repositories
didclaw-client
A set of Cursor instructions for the didclaw client, called lclaw-ui. Cursor rules are project guidance that tell the coding agent about the codebase, commands, implementation practices, and release notes.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.