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/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/naming-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/naming-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/naming-standards/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/jim-schilling/splurge-ai-rules/naming-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/naming-standards.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.00006 | $0.00430 |
| Opus 5 | $0.00003 | $0.00215 |
| Sonnet 5 | $0.00001 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
naming-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 9d 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
- Use descriptive variable names with auxiliary verbs (e.g. is_active, has_permission).
- Use PascalCase for class, enum, and dataclass names (e.g., DsvReader, CsvWriter, TransformXmlToJson).
- For SQL, prefer lower case column names.
- Prefer upper snake case for constant names.
- Environment variable names MUST use a project prefix [A-Z][A-Z0-9_]*_ (e.g., SPLURGE_DSV_).
- Test module names should mirror the domains associated with the modules, where DOMAINS is a list of the module's domain names.
- e.g., for a module that has DOMAINS = ['dsv', 'csv'], the test module should be named test_csv_dsv_[SEQUENCE].py, where [SEQUENCE] is a unique identifier for the test module.
- Test class names should mirror the class being tested, prefixed with Test.
- e.g., for a class named CsvReader, the test class should be named TestCsvReader.
- Test method names should be descriptive and follow the pattern test_[condition]_[expectedResult].
- e.g., test_read_valid_csv_returns_data, test_read_invalid_csv_raises_exception.
- Use verbs for function and method names (e.g., get_data, process_file).
- Use nouns for class and module names (e.g., DataProcessor, file_utils).
- Use singular nouns for class names (e.g., User, Product).
- Use plural nouns for collection names (e.g., Users, Products).
- Test module names should be prefixed with test_ (e.g., test_csv_reader.py).
- For every code module, there shall be at least one corresponding test module in named test_[module-path]_basic.py, where [module-path] is the module path with dots replaced by underscores, the path will not contain the package name.
- e.g., for a module named splurge_unittest_to_pytest.converter.helpers, the test module should be named test_converter_helpers_basic.py.
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.
- 9d ago First seen · 24 lines · 6 tokens per session scan A 2dd157965c83
naming-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 6 tokens to every session and 430 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
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.
cli-error-handling
CLI command error handling 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.