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/httpx)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/httpx"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/httpx.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.02582 | $0.02582 |
| Opus 5 | $0.01291 | $0.01291 |
| Sonnet 5 | $0.00516 | $0.00516 |
| Haiku 4.5 | $0.00258 | $0.00258 |
Grade A, and why
httpx 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
httpx Best Practices
httpx is the de-facto modern HTTP client for Python, offering both synchronous and asynchronous APIs, native HTTP/2 support, and advanced features essential for high-throughput services. Adhere to these guidelines for optimal performance, reliability, and code clarity.
Code Organization and Structure
Always use a Client or AsyncClient instance
Avoid top-level helper functions (httpx.get, httpx.post) for anything beyond simple, one-off scripts. Client instances enable connection pooling, HTTP/2, and persistent configuration.
❌ BAD:
import httpx
# In a loop or repeated calls, this creates new connections every time
for _ in range(5):
response = httpx.get("https://api.example.com/data")
# ... process response
✅ GOOD:
import httpx
# Client is instantiated once and reused
with httpx.Client() as client:
for _ in range(5):
response = client.get("https://api.example.com/data")
# ... process response
Instantiate a single client per process or request scope
Reuse Client/AsyncClient instances. Creating new clients in a hot loop defeats connection pooling and can exhaust resources. Pass a scoped client or use a global instance (with caution in async apps).
❌ BAD:
# In an async web handler, this creates a new client per request
async def get_user_data(user_id: str):
async with httpx.AsyncClient() as client: # Client created per request
response = await client.get(f"https://api.example.com/users/{user_id}")
return response.json()
✅ GOOD:
# Instantiate client once at application startup
# For web frameworks, use dependency injection or app-level state
import httpx
# Global client (careful with stateful clients in multi-tenant apps)
# For web frameworks like FastAPI, prefer dependency injection.
_async_client: httpx.AsyncClient | None = None
async def get_async_client() -> httpx.AsyncClient:
global _async_client
if _async_client is None:
_async_client = httpx.AsyncClient(base_url="https://api.example.com")
return _async_client
async def get_user_data(user_id: str):
client = await get_async_client() # Reuse the same client
response = await client.get(f"/users/{user_id}")
return response.json()
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 · 352 lines · 2,582 tokens per session scan A e1ab362f1ea2
httpx 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 2,582 tokens to every session, about $0.0129 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.
py-fast-api
Cursor rules for Python FastAPI backend development and best practices.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
10-backend-python
Backend Python development rules for FastAPI, SQLAlchemy 2.x, async patterns, and Alembic migrations.