050-cli-dev

Development rules for adding commands to the CamoFox command-line tool, a text-based way to control CamoFox from a terminal.

In plain words
What is it for?
Building or changing CamoFox CLI commands, connecting them to the browser API, handling errors, supporting fallback behavior, and implementing secure authentication options.
Why use it?
They keep commands consistent, validate input, handle compatibility paths, format output predictably, and protect passwords and other secrets.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/redf0x1/camofox-browser/050-cli-dev
Clone the repo
git clone --depth 1 https://github.com/redf0x1/camofox-browser

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 341 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00341
Opus 5 $0.00000 $0.00170
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured 2d ago against content hash e96af3cbc876, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.cursor/rules/050-cli-dev.mdc · 44 lines

What it actually says

CLI Development Conventions

Structure

  • Register commands in src/cli/commands/*.ts grouped by domain.
  • Wire modules in src/cli/index.ts only.
  • 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 resolveCommandUser and default to CLI/global setting.
  • Use printWithOptionalFormat or context formatter for consistent output.

Transport and Fallback

  • Use apiRequestWithFallback / requestWithFallback where 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 --help outputs.
  • Validate JSON/text/plain formatting behavior.
  • Confirm auto-start behavior and server command exclusions in preAction logic.
Changes

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.

  1. 2d ago First seen · 44 lines · 0 tokens per session scan A e96af3cbc876

Subscribe to this mod's changes

050-cli-dev is a cursor rule published in the GitHub repository redf0x1/camofox-browser (377 stars, last pushed 19d 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.