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/crewaigit 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/crewai)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/crewai"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/crewai.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.02108 | $0.02108 |
| Opus 5 | $0.01054 | $0.01054 |
| Sonnet 5 | $0.00422 | $0.00422 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
crewai 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrewAI Best Practices
This document outlines the definitive best practices for developing with CrewAI, ensuring your multi-agent systems are maintainable, performant, and production-ready. Adhere to these guidelines for all new and existing CrewAI projects.
1. Code Organization and Structure
Always modularize your agents, tasks, and crews into dedicated Python modules. This promotes reusability, version control, and clear separation of concerns.
1.1. Dedicated Modules for Agents, Tasks, and Crews
Always separate definitions. Agents belong in agents.py, tasks in tasks.py, and the crew orchestration in crew.py (or main.py).
❌ BAD: Monolithic file
# main.py
from crewai import Agent, Task, Crew
researcher = Agent(role='Researcher', ...)
research_task = Task(description='Research topic', agent=researcher, ...)
crew = Crew(agents=[researcher], tasks=[research_task], ...)
✅ GOOD: Modular structure
# agents.py
from crewai import Agent
from tools import search_tool # Assume tools.py exists
class ResearchAgents:
def senior_researcher(self) -> Agent:
return Agent(
role='Senior Researcher',
goal='Uncover critical insights and data points.',
backstory='Expert in data analysis and synthesis.',
verbose=True, allow_delegation=False, tools=[search_tool]
)
# tasks.py
from crewai import Task
from agents import ResearchAgents
class ResearchTasks:
def __init__(self):
self.agents = ResearchAgents()
def research_topic(self, topic: str) -> Task:
return Task(
description=f"Conduct comprehensive research on '{topic}'.",
expected_output='A detailed report summarizing key findings.',
agent=self.agents.senior_researcher(),
async_execution=False
)
# crew.py
from crewai import Crew, Process
from agents import ResearchAgents
from tasks import ResearchTasks
class MyCrew:
def __init__(self, topic: str):
self.topic = topic
self.agents = ResearchAgents()
self.tasks = ResearchTasks()
def run(self):
crew = Crew(
agents=[self.agents.senior_researcher()],
tasks=[self.tasks.research_topic(self.topic)],
process=Process.sequential,
verbose=2
)
return crew.kickoff()
if __name__ == "__main__":
result = MyCrew("AI Agent Frameworks in 2025").run()
print(result)
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 · 277 lines · 0 tokens per session scan A b623f7003b91
crewai 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,108 tokens to every session, about $0.0105 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.