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/ItamarZand88/awesome-agent-conventionsWrote 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/itamarzand88/awesome-agent-conventions/python)<a href="https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/python"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/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/itamarzand88/awesome-agent-conventions/python"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/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.00765 | $0.00765 |
| Opus 5.5 | $0.00306 | $0.00306 |
| Sonnet 5.5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
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.
This is a copy
94% identical to python — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: "Python best practices and patterns for modern software development with Flask and SQLite" globs: /*.py, src//.py, tests/**/.py alwaysApply: false
Python Best Practices
Project Structure
- Use src-layout with
src/your_package_name/ - Place tests in
tests/directory parallel tosrc/ - Keep configuration in
config/or as environment variables - Store requirements in
requirements.txtorpyproject.toml - Place static files in
static/directory - Use
templates/for Jinja2 templates
Code Style
- Follow Black code formatting
- Use isort for import sorting
- Follow PEP 8 naming conventions:
- snake_case for functions and variables
- PascalCase for classes
- UPPER_CASE for constants
- Maximum line length of 88 characters (Black default)
- Use absolute imports over relative imports
Type Hints
- Use type hints for all function parameters and returns
- Import types from
typingmodule - Use
Optional[Type]instead ofType | None - Use
TypeVarfor generic types - Define custom types in
types.py - Use
Protocolfor duck typing
Flask Structure
- Use Flask factory pattern
- Organize routes using Blueprints
- Use Flask-SQLAlchemy for database
- Implement proper error handlers
- Use Flask-Login for authentication
- Structure views with proper separation of concerns
Database
- Use SQLAlchemy ORM
- Implement database migrations with Alembic
- Use proper connection pooling
- Define models in separate modules
- Implement proper relationships
- Use proper indexing strategies
Authentication
- Use Flask-Login for session management
- Implement Google OAuth using Flask-OAuth
- Hash passwords with bcrypt
- Use proper session security
- Implement CSRF protection
- Use proper role-based access control
API Design
- Use Flask-RESTful for REST APIs
- Implement proper request validation
- Use proper HTTP status codes
- Handle errors consistently
- Use proper response formats
- Implement proper rate limiting
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 · 122 lines · 765 tokens per session scan A dca817c4a670
python is a cursor rule published in the GitHub repository ItamarZand88/awesome-agent-conventions (34 stars, last pushed 2mo ago), licensed MIT. It adds 765 tokens to every session, about $0.0031 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to python, differing in 1 line, and is treated as a copy.
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-flask-json-guide-cursorrules-prompt-file
Cursor rules for Python Flask development with JSON guide.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
py-fast-api
Cursor rules for Python FastAPI backend development and best practices.
python-django-best-practices-cursorrules-prompt-fi
Cursor rules for Python Django development with best practices.
python
Python best practices and patterns for modern software development with Flask and SQLite.