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/design-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/design-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/design-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/design-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/design-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.00004 | $0.00305 |
| Opus 5 | $0.00002 | $0.00152 |
| Sonnet 5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
design-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 8d 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 SOLID (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) principles.
- Follow DRY (Don't Repeat Yourself) principle.
- Follow BDD/TDD (Behavior/Test Driven Development) practices.
- Follow MVP (Minimum Viable Product) approach.
- Follow KISS (Keep It Simple, Stupid) principle.
- Follow PoLA (Principle of Least Authority).
- Follow YAGNI (You Aren't Gonna Need It) principle.
- Prefer composition over inheritance.
- Prefer encapsulation.
- Prefer separation of concerns.
- Prefer to fail fast.
- Follow the Law of Demeter - objects should only interact with their immediate dependencies.
- Prioritize error handling using appropriate mechanisms (exceptions, return values, Result types, or callbacks).
- Use guard clauses to handle preconditions and invalid state early.
- Avoid side effects in module-level code.
- Place the happy path (main successful execution flow) last in the function.
- Use guard clauses and early returns instead of complex if-else chains.
- Prefer iteration and modularization over code duplication.
- Prefer simple, straightforward design over over-engineering.
- Private methods should accept necessary data as parameters rather than directly accessing instance variables.
- Use domain-specific custom exceptions for public APIs.
- Use native/built-in exceptions for low-level APIs, where appropriate.
- Prioritize code clarity while maintaining reasonable efficiency.
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.
- 8d ago First seen · 28 lines · 4 tokens per session scan A 642d7c8d3bde
design-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 305 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
manual-review.backend
A set of rules for verifying backend-only changes and changes that use different verification channels. It separates evidence the agent can collect from checks that require a person, a production authorization, or a business decision.
proactive-skills.design-checkpoint
A rule that makes interface and design checks part of the implementation process whenever pages, components, layouts, or other user-interface files change.
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
common-testing
Testing requirements: 80% coverage, TDD workflow.
tdd
Test-driven development — red-green-refactor cycle.