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/astrogit 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/astro)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/astro"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/astro.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.03071 | $0.03071 |
| Opus 5 | $0.01536 | $0.01536 |
| Sonnet 5 | $0.00614 | $0.00614 |
| Haiku 4.5 | $0.00307 | $0.00307 |
Grade A, and why
astro 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro Best Practices
Astro is a "disappearing" framework designed for shipping zero JavaScript by default, adding interactivity only where needed. Our team leverages Astro for its unparalleled performance and developer experience, especially for content-focused sites. Adhere to these guidelines to maintain a consistent, high-performing, and maintainable codebase.
1. Code Organization and Structure
Maintain a predictable and logical file structure for easy navigation and scaling.
1.1 Standard Project Structure
Always scaffold new projects with the official Astro starter and maintain the following structure:
src/
├── components/ # Reusable UI components (Astro or UI framework islands)
│ ├── ui/ # Generic, framework-agnostic components
│ └── react/ # React-specific components
├── content/ # Markdown/MDX files for Content Collections
├── layouts/ # Base page layouts
├── pages/ # Top-level routes
├── styles/ # Global CSS, utility classes, Tailwind config
├── env.d.ts # Global type declarations
└── astro.config.ts # Type-safe Astro configuration
1.2 Naming Conventions
- Astro Components (
.astro): Usekebab-case. - UI Framework Components (e.g., React
.jsx,.tsx): UsePascalCase. - Pages (
.astro): Usekebab-casefor file names.
❌ BAD
<!-- src/components/MyCard.astro -->
<div class="myCard">...</div>
// src/components/Mycard.jsx
export default function Mycard() { return <div>...</div>; }
✅ GOOD
<!-- src/components/my-card.astro -->
<div class="my-card">...</div>
// src/components/react/MyCard.tsx
export default function MyCard() { return <div>...</div>; }
1.3 TypeScript Configuration
Leverage TypeScript throughout the codebase for type safety, even in .astro components.
tsconfig.json
{
"extends": "astro/tsconfigs/strict",
"compilerOptions": {
"verbatimModuleSyntax": true, // Enforce explicit type imports
"plugins": [
{
"name": "@astrojs/ts-plugin" // Essential for editor support
}
],
"paths": {
"@components/*": ["./src/components/*"],
"@layouts/*": ["./src/layouts/*"],
"@content/*": ["./src/content/*"],
"@styles/*": ["./src/styles/*"]
}
},
"include": [".astro/types.d.ts", "**/*"],
"exclude": ["dist"]
}
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 · 437 lines · 0 tokens per session scan A 26270c4d29a6
astro 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 3,071 tokens to every session, about $0.0154 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
python
Python best practices and patterns for modern software development with Flask and SQLite.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
spec-fn-naming
Spec function naming conventions.
java-17-development-standards
Java-specific development standards following Effective Java, Google Java Style Guide, and modern Java 17 LTS best practices.