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/iloveitaly/llm-ide-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/iloveitaly/llm-ide-rules/python-app)<a href="https://agentmods.dev/rules/iloveitaly/llm-ide-rules/python-app"><img src="https://agentmods.dev/badge/rules/iloveitaly/llm-ide-rules/python-app/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/iloveitaly/llm-ide-rules/python-app"><img src="https://agentmods.dev/badge/rules/iloveitaly/llm-ide-rules/python-app.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.02010 | $0.02010 |
| Opus 5.5 | $0.00804 | $0.00804 |
| Sonnet 5.5 | $0.00402 | $0.00402 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
python-app 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python App
Here's how the python application is organized:
app/lib/is for code that is not specified to this application and with some effort could extracted into a external package.app/helpersis for larger reusable modules that if they weren't specific to this application, could be extracted into their own package.app/utilsare small helper functions that are specific to a particular page or area of the application.app/__init__.pyis the entrypoint for the application which is run when anything is executed (fastapi, celery, etc).- It primarily runs
configure_*commands for anyapp.configuration.*modules. These modules primary setup API clients, database connections, python language configuration, etc. - Also makes sure anything that mutates global state loads early.
- It primarily runs
- FastAPI server and routes are specified in
app/routes/ - SQLModels are specified in
app/models/ - Files within
app/commands/should have:- Are not designed for CLI execution, but instead are interactor-style internal commands.
- Should not be used on the queuing system
- A
performfunction that is the main entry point for the command. - Look at existing commands for examples of how to structure the command.
- Use
TypeIDfor any parameters that are IDs of models.
- Files within
app/jobs/should have:- Are designed for use on the queuing system.
- A
performfunction that is the main entry point for the job. - Look at existing jobs for examples of how to structure the job.
- Use
TypeID | strfor any parameters that are IDs of models.
- When referencing a command, use the full-qualified name, e.g.
app.commands.transcript_deletion.perform. - When queuing a job or
performing it in a test, use the full-qualified name, e.g.app.jobs.transcript_deletion.perform. app/cli/is for scripts or CLI tools that are specific to the application.- Webhooks should be fired in the model layer, not in a router or command.
- Lifecycle logic (status/state transitions, webhook enqueue, access grants) should live on the model. Commands, routes, etc should not re-implement
after_save-style logic. - Alias classes which are commonly used in the application. This makes it easier to grep for instances of that class without worrying about namespace clashes.
- Example:
from botocore.exceptions import ClientError as BotoCoreClientErrorinstead of a plainClientError. BaseModelfromactivemodelis commonly used inmodels/*.py, sopydantic'sBaseModelshould be aliased toPydanticBaseModel
- Example:
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.
- yesterday Changed · +2 lines 12ecbdf5be59
- 12d ago Changed · +36 lines · +292 tokens per session e25783272451
- 19d ago Changed · +3 lines · +101 tokens per session 1ba0ce9e26d1
- 21d ago Changed · -1 lines 80c7c6847d1a
- 27d ago Changed · +7 lines · +93 tokens per session 734e6ad30858
- 1mo ago Changed · +14 lines · +228 tokens per session 6e94cf7698d0
- 1mo ago First seen · 120 lines · 1,296 tokens per session scan A aef4b52e23b3
python-app is a cursor rule published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed yesterday), licensed MIT. It adds 2,010 tokens to every session, about $0.0080 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-30.
Other cursor rules, from other repositories
pyspark-etl-best-practices-cursorrules-prompt-file
Cursor rules for PySpark ETL development with code style, joins, window functions, map operations, and Iceberg patterns.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
automl-hyperparameter-optimization
AutoML and hyperparameter optimization rules for Python ML projects using Ray Tune, Optuna, PyCaret, and time-series AutoML libraries.
agent-model-choice
User-owned model choice and settings notices.
11-prompt-maintainer
Checklist when touching prompt builders, agent fragments, or MCP tool docstrings.
llm-integration-rules
A set of rules for connecting an application to a large language model, including Python wrappers, API endpoints, asynchronous calls, retries, and key management.