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/asp-netgit 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/asp-net)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/asp-net"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/asp-net.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.02658 | $0.02658 |
| Opus 5 | $0.01329 | $0.01329 |
| Sonnet 5 | $0.00532 | $0.00532 |
| Haiku 4.5 | $0.00266 | $0.00266 |
Grade A, and why
asp-net 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
asp-net Best Practices
This document outlines the definitive best practices for developing ASP.NET Core applications within our team. Adhere to these guidelines to ensure consistent, performant, and maintainable backend services.
1. Code Organization and Structure
Organize your projects by feature or bounded context, not by technical layer. This improves cohesion and reduces coupling.
✅ GOOD: Feature-First Organization
// Project structure for a "Product" feature
src/
├── MyProject.Api/
│ ├── Program.cs
│ ├── Features/
│ │ ├── Products/
│ │ │ ├── ProductEndpoints.cs // Minimal API definitions
│ │ │ ├── ProductController.cs // API Controller (if used)
│ │ │ ├── GetProduct.cs // Request/Response DTOs, Handler (e.g., MediatR)
│ │ │ ├── CreateProduct.cs
│ │ │ └── ProductService.cs // Feature-specific business logic
│ ├── Common/ // Shared infrastructure, middleware, extensions
│ │ ├── Filters/
│ │ ├── Middleware/
│ │ └── Extensions/
├── MyProject.Application/ // Application-specific services, interfaces, DTOs
│ ├── Interfaces/
│ ├── Services/
│ └── DTOs/
├── MyProject.Domain/ // Core domain entities, value objects, interfaces
├── MyProject.Infrastructure/ // Data access (EF Core), external services
│ ├── Data/
│ ├── Repositories/
│ └── ExternalServices/
└── MyProject.Tests/ // Unit and Integration tests
❌ BAD: Layer-First Organization
// Avoid this structure for larger applications
src/
├── MyProject.Api/
│ ├── Controllers/ // All controllers here
│ ├── Services/ // All services here
│ ├── Repositories/ // All repositories here
│ └── DTOs/ // All DTOs here
2. API Design: Minimal APIs vs. API Controllers
Always prefer Minimal APIs for new endpoints due to their simplicity and directness. Use API Controllers only when you require advanced features like automatic model binding from multiple sources, built-in validation attributes, or complex attribute routing that Minimal APIs don't easily provide.
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 · 358 lines · 0 tokens per session scan A cdd67f02683a
asp-net 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,658 tokens to every session, about $0.0133 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
aspnet-abp-cursorrules-prompt-file
Cursor rules for Aspnet Abp.
kraken-net
Conventions for using Kraken.Net when working with Kraken Spot and Futures cryptocurrency exchange APIs in C#/.NET. Apply when generating code that interacts with Kraken API.
ef-core
Entity Framework Core patterns - DbContext, repositories, migrations, query optimization.
unity-core
// ✅ DO: PascalCase public class PlayerController : MonoBehaviour { }.
cfx-csharp-conventions
Coding conventions for C# scripts in FiveM and RedM resources.
unity-game-developer-intelligent
Expert Unity game developer specializing in C# scripting, 3D graphics, mobile optimization, and complete game development workflows. Apply this rule when working on Unity projects, implementing Unity C# scripts, designing component-based architecture, optimizing Unity performance, building Unity UI systems…