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/pytest)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/pytest"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/pytest.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.01879 | $0.01879 |
| Opus 5 | $0.00940 | $0.00940 |
| Sonnet 5 | $0.00376 | $0.00376 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
pytest 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 3d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pytest Best Practices
This document outlines our team's standard for writing pytest tests. Adhering to these guidelines ensures our test suite is fast, reliable, and easy to maintain, integrating seamlessly into our CI/CD pipelines.
1. Code Organization & Structure
1.1 Project Layout
Always use the src/ layout for your project. This prevents common import pitfalls and ensures tests run against the installed package, not local source.
✅ GOOD:
.
├── pyproject.toml
├── src/
│ └── mypackage/
│ ├── __init__.py
│ └── module.py
└── tests/
├── __init__.py
└── test_module.py
❌ BAD:
.
├── pyproject.toml
├── mypackage/ # Top-level package
│ ├── __init__.py
│ └── module.py
└── tests/
└── test_module.py
1.2 Test File Naming
Name test files test_*.py or *_test.py. We prefer test_*.py.
Place __init__.py files in tests/ and its subdirectories to treat them as Python packages, enabling structured imports and avoiding name collisions.
✅ GOOD:
# tests/test_my_feature.py
from mypackage.module import my_function
def test_my_function_returns_expected_value():
assert my_function() == "expected"
1.3 Test Naming Conventions
Prefix test functions and methods with test_. For classes, prefix with Test. Use descriptive names that read like sentences.
✅ GOOD:
def test_user_can_be_created_with_valid_email():
# ...
pass
class TestUserService:
def test_get_user_by_id_returns_correct_user():
# ...
pass
❌ BAD:
def create_user(): # Not discovered by pytest
pass
def test_create_user_and_email(): # Tests multiple things
pass
class UserServiceTest: # Incorrect class prefix
pass
2. Common Patterns & Anti-patterns
2.1 Single Assert Per Test
Each test should verify one specific behavior. This improves readability and simplifies debugging.
✅ GOOD:
def test_user_creation_sets_email():
user = create_user("[email protected]")
assert user.email == "[email protected]"
def test_user_creation_sends_welcome_email():
user = create_user("[email protected]")
assert email_service.last_sent_email == "[email protected]"
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.
- 3d ago First seen · 263 lines · 1,879 tokens per session scan A d5f01ee429e9
pytest 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,879 tokens to every session, about $0.0094 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-cursorrules-prompt-file-best-practices
Cursor rules for Python development with best practices integration.
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.
python-tests
Tests and coverage when changing src/, scripts/, or tests/.
python
Python development guidelines — PEP 8, type hints, error handling, async patterns, packaging, and testing. Applied when working with Python code.
python-code-validator
Validate generated Python at every step, not once at the end.
pytest
You are an expert in pytest testing. Follow these rules.