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.
git 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/scrapy)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/scrapy"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/scrapy.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.1 | $0.04254 | $0.04254 |
| Opus 5 | $0.02127 | $0.02127 |
| Sonnet 5 | $0.00851 | $0.00851 |
| Haiku 4.5 | $0.00425 | $0.00425 |
Grade A, and why
scrapy 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 4d 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 — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrapy Best Practices
Scrapy is the definitive framework for high-performance web scraping in Python. This guide outlines the essential practices for building resilient, scalable, and ethical crawlers. Adhere to these guidelines to ensure your Scrapy projects are maintainable, efficient, and robust against the dynamic web landscape of 2025.
1. Code Organization and Structure
Maintain a clean, logical project structure. This enhances readability, testability, and scalability.
1.1. Standard Project Layout
Always use scrapy startproject to initialize your project. This sets up the recommended directory structure.
❌ BAD: Manually creating files and directories
# Don't do this
mkdir my_scraper
cd my_scraper
touch scrapy.cfg items.py spiders/__init__.py ...
✅ GOOD: Use the Scrapy CLI
scrapy startproject my_project_name
cd my_project_name
1.2. Item Definitions (items.py)
Define your data models clearly using scrapy.Item subclasses. Always include type hints for better IDE support and code clarity.
❌ BAD: Generic dictionaries or untyped Item fields
# items.py
import scrapy
class ProductItem(scrapy.Item):
title = scrapy.Field()
price = scrapy.Field()
# No type hints, hard to know expected data type
✅ GOOD: scrapy.Item with Field and typing hints
# items.py
import scrapy
from scrapy.item import Field
from typing import Optional, List
class ProductItem(scrapy.Item):
url: str = Field()
title: Optional[str] = Field()
price: Optional[float] = Field()
description: Optional[str] = Field()
image_urls: List[str] = Field()
category: Optional[str] = Field()
1.3. Spiders
Keep spiders focused on crawling logic and initial data extraction. They should yield Request objects and Item objects.
❌ BAD: Complex data processing or storage logic in spiders
# spiders/bad_spider.py
import scrapy
from my_project_name.items import ProductItem
class BadSpider(scrapy.Spider):
name = "bad_spider"
start_urls = ["http://example.com"]
def parse(self, response):
item = ProductItem()
item['title'] = response.css('h1::text').get()
# ... complex cleaning and validation here ...
# ... database insertion logic here ...
yield item
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.
- 4d ago First seen · 530 lines · 4,254 tokens per session scan A 0f682060f625
scrapy 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 4,254 tokens to every session, about $0.0213 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-09-03.
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.