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/security-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/security-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/security-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/security-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.00006 | $0.00185 |
| Opus 5 | $0.00003 | $0.00093 |
| Sonnet 5 | $0.00001 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
security-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 6d 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
- Follow secure coding best practices.
- Validate and sanitize all user inputs to prevent injection attacks (SQL, Shell, XSS, command injection).
- Use parameterized queries and prepared statements for database operations.
- Implement proper authentication and authorization mechanisms.
- Never store sensitive data (passwords, API keys, tokens) in plain text.
- Follow the principle of least privilege for user permissions and API access.
- Implement comprehensive error handling without exposing sensitive information.
- Restrict allowed file types and sizes.
- Use secure random number generators for cryptographic operations.
- Implement proper logging without logging sensitive information.
- Follow OWASP security guidelines and address common vulnerabilities.
- Use environment variables or secure vaults for configuration secrets.
- Implement proper password policies and secure password hashing.
- Follow secure API design principles (proper HTTP methods, versioning, etc.).
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.
- 6d ago First seen · 19 lines · 6 tokens per session scan A 1c685b8c3cc9
security-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 185 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.