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/inboxpraveen/Minimize-Cursor-CostWrote 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/inboxpraveen/minimize-cursor-cost/python)<a href="https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/python"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/python/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/inboxpraveen/minimize-cursor-cost/python"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/python.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.00000 | $0.00224 |
| Opus 5.5 | $0.00000 | $0.00090 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
python 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
Python-Specific Rules
Style
- Match existing style: black-formatted or not, docstring style, type hint usage
- Don't add type hints where none exist unless asked
- Don't reformat existing code while fixing something unrelated
Output
- For single-function edits: show only that function
- For class edits: show only the changed method(s)
- Use
# ... rest of class unchangedto skip
Imports
- Show only net-new import lines needed
- Do not reprint the full import block
Common shortcuts
- If a pattern repeats across methods, note it once:
# same pattern as create_x() - Prefer list comprehensions over loops unless the existing code uses loops
- Match existing error handling style (bare except vs specific exceptions)
Never
- Don't add
if __name__ == "__main__"unless asked - Don't add logging setup unless asked
- Don't convert functions to async unless asked
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 · 32 lines · 0 tokens per session scan A 32cfff350e61
python is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (10 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 224 tokens. 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
010-python-tooling
Python tooling and dependency conventions for plugin-eval and tools/.
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
10-backend-fastapi
FastAPI backend rules.
django
Django: models, views, ORM best practices.
python
Python best practices: type hints, pathlib, pytest, clean error handling.
pydantic
Pydantic: BaseModel, validators, Field, Settings.