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 agentmods add rules/redf0x1/camofox-browser/030-workflowsgit clone --depth 1 https://github.com/redf0x1/camofox-browserWhat 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 | $0.00540 | $0.00540 |
| Opus 5 | $0.00270 | $0.00270 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
030-workflows scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
## 5) API + curl Workflow How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CamoFox Workflow Patterns
1) Basic Interaction Loop
camofox open https://example.com # open tab
camofox snapshot # get refs
camofox click e5 # click
camofox type e7 "hello" # type
camofox snapshot # refresh refs
2) Search Workflow
camofox open https://google.com # create tab
camofox search "camofox" --engine google # navigate to search results
camofox snapshot # inspect result refs
3) Login Workflow (Vault-Safe)
camofox auth save account --url https://service.com/login # store encrypted credentials
camofox open https://service.com/login # open login page
camofox snapshot # get username/password refs
camofox auth load account --inject --username-ref e5 --password-ref e9 # inject without stdout leaks
4) Pipeline Workflow
camofox run login-flow.txt # run file
camofox run login-flow.txt --continue-on-error # keep going after failures
echo "get-url" | camofox run - # stdin pipeline
5) API + curl Workflow
curl -X POST http://localhost:9377/tabs \
-H 'Content-Type: application/json' \
-d '{"userId":"agent1","sessionKey":"task1","url":"https://example.com"}'
curl "http://localhost:9377/tabs/<tabId>/snapshot?userId=agent1"
6) Session Restore Workflow
camofox session save before-login # save cookies
# ... close/restart ...
camofox session load before-login # restore cookies to tab
7) CAPTCHA / Visual Intervention Workflow
curl -X POST http://localhost:9377/sessions/agent1/toggle-display \
-H 'Content-Type: application/json' \
-d '{"headless":"virtual"}' # restart with noVNC
# solve challenge manually via returned vncUrl
curl -X POST http://localhost:9377/sessions/agent1/toggle-display \
-H 'Content-Type: application/json' \
-d '{"headless":true}' # return to headless
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.
- 3d ago First seen · 65 lines · 540 tokens per session scan A b22fae53004c
030-workflows is a cursor rule published in the GitHub repository redf0x1/camofox-browser (381 stars, last pushed 21d ago), licensed MIT. It adds 540 tokens to every session, about $0.0027 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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
invictum-browser
Use Invictum Browser Bridge whenever the user requests IBB, IBG, Invictum Browser Bridge, or Invictum Browser Gate.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.