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/project-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/project-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/project-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.1 | $0.00004 | $0.00194 |
| Opus 5 | $0.00002 | $0.00097 |
| Sonnet 5 | $0.00001 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
project-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 7d 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
- Create top-level folder: docs/.
- Create project README.md which summarizes the project.
- Create project CHANGELOG.md which details changes for each version/feature-branch.
- Create docs/README-DETAILS.md which details project features, usage, errors, dependencies, etc.
- Create sub-folders under docs/: research/, plans/, specs/, issues/, apis/, notes/, configuration/.
- For code projects, create top-level folders: tests/, examples/, scripts/, and tools/.
- For code projects, create sub-folders under tests/: unit/, integration/, e2e/.
- For Python projects, create modern, standardized pyproject.toml.
- For Python projects, use CalVer versioning.
- License shall be MIT.
- Author and Maintainer shall be Jim Schilling.
- Project base url shall be http://github.com/jim-schilling/[REPOSITORY].
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.
- 7d ago First seen · 18 lines · 4 tokens per session scan A 60dd2e032479
project-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 194 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.