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/jim-schilling/splurge-ai-rules/cli-standardsgit clone --depth 1 https://github.com/jim-schilling/splurge-ai-rulesWrote 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/jim-schilling/splurge-ai-rules/cli-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/cli-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/cli-standards.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 | $0.00004 | $0.00299 |
| Opus 5 | $0.00002 | $0.00150 |
| Sonnet 5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
cli-standards 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 4d 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
- MUST accept text input via stdin, arguments or files.
- May accept environment variables for configuration, unless user opts out.
- Sensitive data must use environment variables.
- Environment variable names MUST use a project prefix [A-Z][A-Z0-9_]*_ (e.g., SPLURGE_DSV_).
- Provide --output-format {table,json, and/or ndjson} (default: table).
- When reading from stdin, a file path of - MUST mean "read from stdin".
- Stdout and stderr MUST be UTF-8 encoded without BOM.
- Exit codes: 0 success; 1 generic error; 2 invalid arguments; 130 interrupted (Ctrl+C).
- Flags map by prefix + uppercasing + hyphens→underscores (e.g., --api-token → SPLURGE_DSV_API_TOKEN).
- JSON output formats:
--output-format json: Output complete JSON arrays, one per line--output-format ndjson: Output one JSON object per line (newline-delimited)- Never mix JSON with other text on stdout
- If an env var is referenced but missing, fail fast: "Missing required environment variable: ".
- Redact sensitive data for output, logging, and errors.
- Document defaults in --help output.
- CLI arguments override environment variables.
- Environment variables override built-in defaults.
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.
- 4d ago First seen · 23 lines · 4 tokens per session scan A 8e79bd8294b3
cli-standards is a cursor rule published in the GitHub repository jim-schilling/splurge-ai-rules (3 stars, last pushed 11mo ago), licensed MIT. It adds 4 tokens to every session and 299 once invoked, about $0.0000 per session on Opus 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-31.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.