awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdc/bottlegit clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/bottle)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/bottle"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/bottle.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.03604 | $0.03604 |
| Opus 5 | $0.01802 | $0.01802 |
| Sonnet 5 | $0.00721 | $0.00721 |
| Haiku 4.5 | $0.00360 | $0.00360 |
Grade A, and why
bottle 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bottle Best Practices
Bottle is a robust micro-framework for Python backends. To leverage it effectively in 2025, adhere to these opinionated guidelines, focusing on structure, maintainability, and security.
1. Code Organization and Structure
Organize your Bottle project as a Python package with a clear separation of concerns. Avoid monolithic app.py files.
✅ GOOD: Modular Project Structure
my_bottle_app/
├── app.py # Application entry point, config loading, plugin setup
├── routes/ # API endpoint definitions
│ ├── __init__.py
│ └── users.py
│ └── products.py
├── services/ # Business logic, database interactions
│ ├── __init__.py
│ └── user_service.py
│ └── product_service.py
├── schemas/ # Pydantic models for request/response validation
│ ├── __init__.py
│ └── user_schema.py
├── config/ # Configuration files (e.g., default.ini)
│ └── default.ini
├── tests/ # Unit and integration tests
│ └── test_users.py
└── requirements.txt
❌ BAD: Monolithic app.py
# app.py (❌ BAD)
from bottle import route, run, request, Bottle
app = Bottle()
# All routes, logic, and config in one file
@app.route('/users', method='GET')
def get_users():
# ... database logic, business logic, everything here ...
return {'users': []}
# ... many more routes and intertwined logic ...
if __name__ == '__main__':
run(app, host='localhost', port=8080)
✅ GOOD: Structured app.py and routes/users.py
# my_bottle_app/app.py (✅ GOOD)
import os
from bottle import Bottle, run
from my_bottle_app.routes import users
from my_bottle_app.plugins.db import DatabasePlugin # Example plugin
app = Bottle()
# 1. Load default config
app.config.load_config('my_bottle_app/config/default.ini')
# 2. Override with environment variables
app.config['database.url'] = os.environ.get('DATABASE_URL', app.config.get('database.url'))
app.config['debug'] = bool(os.environ.get('DEBUG', app.config.get('debug', False)))
# 3. Install plugins
app.install(DatabasePlugin(app.config['database.url']))
# 4. Mount route modules
app.mount('/users', users.app) # users.app is a Bottle instance from routes/users.py
if __name__ == '__main__':
run(app, host='0.0.0.0', port=8080, debug=app.config['debug'])
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.
- 6d ago First seen · 507 lines · 0 tokens per session scan A e93ef904da61
bottle is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 3,604 tokens to every session, about $0.0180 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-30.
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
通用的 Python 和 Django 规则,专注于编码风格、错误处理和整个项目的 Django 约定。.
python-general-coding-standards
应用一般 Python 编码标准,包括类型提示、使用 Pydantic 进行输入验证、后台任务、CORS 处理、安全工具、PEP 8 合规性和全面测试。.