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/autogengit 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/autogen)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/autogen"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/autogen.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.02008 | $0.02008 |
| Opus 5 | $0.01004 | $0.01004 |
| Sonnet 5 | $0.00402 | $0.00402 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
autogen 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autogen Best Practices
Building robust autogen applications requires disciplined adherence to specific patterns. This guide outlines the definitive best practices for our team, focusing on modularity, performance, and testability.
1. Code Organization and Agent Structure
Organize your agents into dedicated modules, ensuring each agent has a single, well-defined responsibility. This mirrors traditional software architecture and enhances maintainability.
❌ BAD: Monolithic agent definitions or generic names.
# agents.py
from autogen import AssistantAgent, UserProxyAgent
# Too many responsibilities, unclear role
def create_complex_agent(llm_config):
agent = AssistantAgent(
name="GenericAgent",
llm_config=llm_config,
system_message="I can do anything you ask."
)
return agent
✅ GOOD: Dedicated modules, clear roles, and explicit system messages.
# agents/planner.py
from autogen import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
def create_planner_agent(model_client: OpenAIChatCompletionClient) -> AssistantAgent:
"""
Creates an agent responsible for breaking down complex tasks into actionable steps.
"""
return AssistantAgent(
name="TaskPlanner",
model_client=model_client,
description="An expert in breaking down complex problems into a sequence of manageable sub-tasks.",
system_message=(
"You are a meticulous TaskPlanner. Your sole responsibility is to decompose user requests "
"into a clear, ordered list of steps. Do not execute tasks, only plan them."
)
)
# agents/coder.py
from autogen import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
def create_coder_agent(model_client: OpenAIChatCompletionClient) -> AssistantAgent:
"""
Creates an agent capable of writing and executing Python code.
"""
return AssistantAgent(
name="PythonCoder",
model_client=model_client,
description="An expert Python programmer capable of writing, executing, and debugging code.",
system_message=(
"You are an expert Python programmer. You write clean, efficient, and well-tested code. "
"When asked to solve a problem, provide the Python code in a markdown block. "
"If execution is needed, state 'EXECUTE' after the code block."
)
)
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 · 263 lines · 0 tokens per session scan A bc52fa5faa00
autogen 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,008 tokens to every session, about $0.0100 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.