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/method-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/method-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/method-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/method-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.00005 | $0.00243 |
| Opus 5 | $0.00003 | $0.00121 |
| Sonnet 5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
method-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 5d 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
- Prefer parameters in method signatures and method calls to be listed on separate lines.
- For classmethods, property methods, and class instance method calls with 3 or more parameters, prefer named keywords for default parameters.
- For standard methods and staticmethods calls with 2 or more parameters, prefer named keywords for default parameters.
- For all other method signatures prefer use of keywords for more than 1 parameter.
- If a method signature use keywords, then all default parameters should be keywords.
- For method signatures with more than 2 parameters, place each parameter on a separate line:
def process_data( input_file: str, output_format: str, validate_schema: bool = True ) -> dict: - For method calls with more than 2 parameters, place each parameter on a separate line:
result = process_data( input_file="data.json", output_format="ndjson", validate_schema=Trues ) - When updating a method or class signature, do not maintain backwards compatibility unless specifically told to do so.
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.
- 5d ago First seen · 28 lines · 5 tokens per session scan A e237e0312db6
method-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 5 tokens to every session and 243 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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.