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/python-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/python-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/python-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/python-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/python-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.00005 | $0.00421 |
| Opus 5.5 | $0.00002 | $0.00168 |
| Sonnet 5.5 | $0.00001 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
python-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 1mo 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
- Always add type annotations to function and method signatures.
- Add type annotations to variables when it improves code clarity.
- Prefer | instead of Optional or Union.
- Code concise, technical, Python that adheres to PEP 8, PEP 604, and PEP 585.
- Code to modern Python standards targeting version 3.10 or later.
- Use absolute import paths, where appropriate.
- When possible, place imports at top of module.
- Group and sort imports: standard libraries, then third-party libraries, then local libraries. Sort alphabetically within each group.
- Use separate statements for multiple context managers instead of nesting them.
- Use mypy for type validation.
- Use ruff for style, formatting, and security validation.
- Place module-level constants in UPPER_SNAKE_CASE.
- Place a single space before and after operators (=, +, -, *, /, ==, !=, <, >, <=, >=, etc.).
- Place a single space after commas in lists, tuples, and function parameters.
- Use 4 spaces for indentation, no tabs.
- Use UTF-8 encoding without BOM for all text files.
- Use f-strings for string interpolation.
- Use triple double quotes for docstrings and comments.
- Use single quotes for string literals, except when the string contains single quotes.
- Add a DOMAINS list at the top of each module indicating associated domains (e.g., DOMAINS = ["generator", "helpers"]).
- Add a package level constant domains listing all associated domains for the package in init.py.
- Use exceptions for error handling, not return codes.
- Use logging module for logging, not print statements.
- Use pathlib for file and path operations.
- Use context managers for file operations.
- Use list comprehensions and generator expressions for creating lists and iterators.
- Use enumerate() when needing both index and value in loops.
- Use zip() to iterate over multiple iterables in parallel.
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.
- 1mo ago First seen · 34 lines · 5 tokens per session scan A c7a60995c70f
python-standards is a cursor rule published in the GitHub repository jim-schilling/splurge-ai-rules (3 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 421 once invoked, about $0.0000 per session on Opus 5.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
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
python-django-general
General coding guidance for Python and Django projects, including naming, formatting, modular apps, built-in tools, and maintainable structure. Python is a programming language, and Django is a Python web framework.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.