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/050-cli-dev)<a href="https://agentmods.dev/rules/redf0x1/camofox-browser/050-cli-dev"><img src="https://agentmods.dev/badge/rules/redf0x1/camofox-browser/050-cli-dev/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/050-cli-dev"><img src="https://agentmods.dev/badge/rules/redf0x1/camofox-browser/050-cli-dev.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.00000 | $0.00341 |
| Opus 5.5 | $0.00000 | $0.00136 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
050-cli-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 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
CLI Development Conventions
Structure
- Register commands in
src/cli/commands/*.tsgrouped by domain. - Wire modules in
src/cli/index.tsonly. - Keep command handlers thin: parse input, call transport, format output.
Command Design
- Prefer
.argument()+.option()signatures with explicit validation. - Support active tab fallback for optional
[tabId]where relevant. - Resolve user via
resolveCommandUserand default to CLI/global setting. - Use
printWithOptionalFormator context formatter for consistent output.
Transport and Fallback
- Use
apiRequestWithFallback/requestWithFallbackwhere legacy paths exist. - Handle 404 fallback explicitly for compatibility branches.
- Keep fallback logic deterministic and minimal.
Error Handling
- Route all errors to
context.handleError. - Throw actionable validation errors for bad CLI input.
- Avoid leaking secrets in errors or logs.
Auth Vault Safety
- Never print decrypted passwords to stdout.
- For
--inject, require explicit username/password refs. - Keep password values in narrow scope and wipe best-effort buffers.
TypeScript Practices
- Preserve strict typing for command options and action handlers.
- Avoid
any; use narrow records/interfaces for payloads. - Keep helpers pure when possible.
Testing/Validation
- Verify help text and command signatures with
--helpoutputs. - Validate JSON/text/plain formatting behavior.
- Confirm auto-start behavior and
servercommand exclusions in preAction logic.
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 · 44 lines · 0 tokens per session scan A e96af3cbc876
050-cli-dev is a cursor rule published in the GitHub repository redf0x1/camofox-browser (423 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 341 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
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-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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.