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/060-routes-devgit 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/060-routes-dev)<a href="https://agentmods.dev/rules/redf0x1/camofox-browser/060-routes-dev"><img src="https://agentmods.dev/badge/rules/redf0x1/camofox-browser/060-routes-dev.svg" alt="Measured on agentmods" 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.00000 | $0.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
060-routes-dev 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 6d 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
Route Development Conventions
Route Files
- Keep core API in
src/routes/core.tsand OpenClaw compatibility insrc/routes/openclaw.ts. - Preserve endpoint compatibility unless a versioned migration is planned.
Request Validation
- Validate required fields early and return
400on malformed input. - Keep user-scoped tab lookup consistent (
findTabById(tabId, userId)). - Enforce request body limits for evaluation endpoints.
Concurrency and Timeouts
- Use
withUserLimitandwithTimeoutfor heavy tab operations. - Use
withTabLockfor tab-mutating actions. - Respect config-driven limits from
loadConfig().
Auth and Security
- Apply conditional API-key checks where currently defined.
- Apply admin-key checks for destructive server controls (
/stop). - Sanitize cookie payloads and enforce bounds.
Response Shape
- Keep responses stable for CLI and OpenClaw clients.
- Include
okand useful context fields when practical. - Avoid returning raw internal errors; use safe error wrappers.
Download/Resource Routes
- Keep user ownership checks on download lookup/content/delete.
- Enforce limits on blob resolution arrays and payload sizes.
Logging
- Use structured
log()calls with req context when available. - Log operation failures with concise, non-sensitive details.
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.
- 6d ago First seen · 40 lines · 0 tokens per session scan A 8b3d39d280b0
060-routes-dev is a cursor rule published in the GitHub repository redf0x1/camofox-browser (383 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 308 tokens. 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
12-skill-repo-scout
SKILL: Scan Backend Repo & Catalog API Surface (use for /repo-scout).
api-patterns
Cursor rule "api-patterns" from LeadMagic/smartlead-mcp-server, covering 🏗️ smartlead api development patterns & best practices, 🎯 quick reference, 🔥 most important patterns, 🏗️ smartlead api client architecture and 🛠️ base client pattern.
external-apis
When calling external APIs.
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.