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/redf0x1/camofox-browserWrote 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/redf0x1/camofox-browser/001-camofox-core)<a href="https://agentmods.dev/rules/redf0x1/camofox-browser/001-camofox-core"><img src="https://agentmods.dev/badge/rules/redf0x1/camofox-browser/001-camofox-core/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/redf0x1/camofox-browser/001-camofox-core"><img src="https://agentmods.dev/badge/rules/redf0x1/camofox-browser/001-camofox-core.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.00446 | $0.00446 |
| Opus 5.5 | $0.00178 | $0.00178 |
| Sonnet 5.5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
001-camofox-core 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 2mo 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
CamoFox Core Rules
What CamoFox Is
- CamoFox Browser is an anti-detection browser automation server built on Camoufox.
- Primary interface is REST API on port
9377with CLI wrappercamofox. - OpenClaw-compatible routes are available (
/tabs/open,/navigate,/snapshot,/act).
Snapshot-First Workflow (Required)
- Open/create a tab.
- Capture snapshot to get current
eNrefs. - Interact using refs when possible.
- Re-snapshot after navigation or major UI updates.
Never assume old refs remain valid after:
- navigation
- modal transitions
- SPA rerenders
- display mode toggles
Element Refs (eN) Rules
- Refs are produced by snapshot endpoints and are user/tab scoped.
- Refs are preferred over selectors for robust automation.
- Treat refs as ephemeral state, not permanent IDs.
User/Session Rules
- Always keep
userIdconsistent through a flow. sessionKey(or legacylistItemId) groups tabs by task.DELETE /sessions/:userIdis the full cleanup operation.
Server Basics
- Health check:
GET /health. - Presets list:
GET /presets. - Context display toggle:
POST /sessions/:userId/toggle-display.
Critical Safety Rules
- If
CAMOFOX_API_KEYis configured, provide Bearer auth for protected routes. - OpenClaw
POST /stopalways requiresx-admin-key, and it must match configured admin key value. - Use
--format jsonfor machine parsing.
Quick Reference
camofox open https://example.com # create tab
camofox snapshot # get refs
camofox click e5 # interact by ref
camofox type e8 "hello" # type text
camofox get-url --format json # structured output
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.
- 2mo ago First seen · 53 lines · 446 tokens per session scan A 18d777509e07
001-camofox-core is a cursor rule published in the GitHub repository redf0x1/camofox-browser (434 stars, last pushed 6d ago), licensed MIT. It adds 446 tokens to every session, about $0.0018 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 cursor rules, from other repositories
real-browser-mcp
Instructions for using Real Browser MCP to control the user's actual browser.
browser-controller
Instructions for using Browser Controller to control the user's actual browser.
invictum-browser
Use Invictum Browser Bridge whenever the user requests IBB, IBG, Invictum Browser Bridge, or Invictum Browser Gate.
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.