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/digitaloceangit 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/digitalocean)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/digitalocean"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/digitalocean.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.02554 | $0.02554 |
| Opus 5 | $0.01277 | $0.01277 |
| Sonnet 5 | $0.00511 | $0.00511 |
| Haiku 4.5 | $0.00255 | $0.00255 |
Grade B, and why
digitalocean scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt update && sudo apt install postgresql postgresql-contrib How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
digitalocean Best Practices
This guide outlines the definitive best practices for developing and deploying applications on DigitalOcean. Adhering to these rules ensures your projects are secure, performant, scalable, and maintainable, leveraging DigitalOcean's managed services and cloud-native patterns.
1. VPC-Centric Networking (Security & Simplicity)
ALWAYS isolate your infrastructure within Virtual Private Clouds (VPCs). This is the cornerstone of secure and efficient communication between your services. Connect all compute resources (Droplets, Kubernetes nodes, Functions) and managed services (Databases) within the same VPC.
-
Connect Managed Databases via VPC: Use the private connection string and add the VPC's CIDR block as the only trusted source. This drastically reduces the attack surface and simplifies IP management.
❌ BAD: Public database connections, individual IP trusted sources.
-- Public connection string, exposed to the internet psql "postgresql://doadmin:[email protected]:25060/defaultdb?sslmode=require"✅ GOOD: Private VPC connection, CIDR block trusted source.
-- Private connection string, only accessible within the VPC psql "postgresql://doadmin:[email protected]:25060/defaultdb?sslmode=require"Configuration: In DigitalOcean Control Panel, for your database, add your VPC's CIDR (e.g.,
10.108.0.0/20) to Trusted Sources. -
All Compute in VPC: Ensure all Droplets, Kubernetes nodes, and Functions are launched within the same VPC as your managed services.
2. Microservices-First Architecture
Embrace a microservices architecture for agility, scalability, and resilience. DigitalOcean provides excellent platforms for this.
- Managed Kubernetes (DOKS) for Orchestration: For complex, containerized applications requiring fine-grained control and high availability.
- App Platform for Rapid CI/CD: For web apps, APIs, and static sites needing fast, automated deployments with integrated CI/CD. Ideal for AI-assisted development workflows (e.g., with Claude Code).
- Premium CPU-Optimized Droplets: For high-performance, resource-intensive workloads that benefit from dedicated CPU.
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 · 262 lines · 0 tokens per session scan B a7bd9dbb9b00
digitalocean 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,554 tokens to every session, about $0.0128 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.