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/azuregit 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/azure)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/azure"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/azure.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.00316 | $0.00316 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
azure 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.
What it actually says
Azure Best Practices
This guide provides opinionated, actionable best practices for developing and operating solutions on Azure. It emphasizes the Azure Well-Architected Framework (Cost Optimization, Security, Reliability, Performance Efficiency, Operational Excellence) and the Microsoft Cloud Adoption Framework (CAF) for governance. Adhere to these standards to build robust, secure, and cost-effective cloud-native applications.
1. Code Organization and Structure
Always use Infrastructure-as-Code (IaC) for Azure resource deployment. Prefer modular, reusable components.
1.1. Modular IaC with Bicep or Terraform
Break down infrastructure into logical, reusable modules. This improves maintainability, reusability, and enforces consistency.
❌ BAD: Monolithic ARM templates or single large Bicep/Terraform files.
// main.bicep - too many resources, hard to manage
resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
// ... all storage config
}
resource appServicePlan 'Microsoft.Web/serverfarms@2022-09-01' = {
// ... all app service plan config
}
// ... many more resources
✅ GOOD: Modular Bicep (or Terraform modules).
// main.bicep
module storage '
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 · 31 lines · 0 tokens per session scan A a5298e6a75fe
azure 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 316 tokens to every session, about $0.0016 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
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
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.