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/blackgit 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/black)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/black"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/black.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.01755 | $0.01755 |
| Opus 5 | $0.00877 | $0.00877 |
| Sonnet 5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00176 | $0.00176 |
Grade A, and why
black 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 5d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
black Best Practices
black is the uncompromising Python code formatter. Our team adopts black as the definitive style guide for all Python projects. By using black, you cede control over formatting minutiae, gaining speed, determinism, and freedom from style debates.
🚨 IMPORTANT: For new projects, or if migrating, strongly consider Ruff instead of black. Ruff offers superior performance and combines formatting, linting, and import sorting into a single tool. If your project is already committed to black, these guidelines apply.
1. Core Principle: Cede Control
black is opinionated by design. Do not fight its formatting. Embrace its defaults to achieve ultimate consistency across the codebase.
2. Installation and Configuration
Always install the latest stable version of black (v25.12.0 as of Dec 2025) and configure it via pyproject.toml.
2.1. Project Dependency
Declare black as a development dependency.
❌ BAD: Global installation or missing dependency
# pyproject.toml
# black not listed, relies on global install or manual management
✅ GOOD: black as a development dependency
# pyproject.toml
[project]
name = "my-project"
version = "0.1.0"
[tool.poetry.dependencies]
python = ">=3.10,<3.13"
[tool.poetry.group.dev.dependencies]
black = "^25.12.0" # Always pin to latest major/minor
2.2. pyproject.toml Configuration
Stick to black's defaults. Only configure line length if absolutely necessary for legacy reasons (e.g., integrating with an older codebase that has a different standard).
❌ BAD: Over-configuring black
# pyproject.toml
[tool.black]
line-length = 100 # Deviating from 88 without strong reason
skip-string-normalization = true # Disabling core black features
✅ GOOD: Minimal black configuration (default 88 chars)
# pyproject.toml
[tool.black]
# No configuration needed; defaults are best.
# If you must change line-length, do so sparingly:
# line-length = 88
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.
- 5d ago First seen · 241 lines · 0 tokens per session scan A a4df830e4371
black 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 1,755 tokens to every session, about $0.0088 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-django-general
通用的 Python 和 Django 规则，专注于编码风格、错误处理和整个项目的 Django 约定。.
python-general-coding-standards
应用一般 Python 编码标准，包括类型提示、使用 Pydantic 进行输入验证、后台任务、CORS 处理、安全工具、PEP 8 合规性和全面测试。.
httpx
Example context from httpx/urlparse.py (lines 153-163).
python-3-brutal-audit
Phase-based brutal audit workflow for Python projects - on-demand architectural review.
sqlmodel
Satisfying the type checker when working with SQLModel.