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.
git 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/htmx)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/htmx"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/htmx.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.02404 | $0.02404 |
| Opus 5 | $0.01202 | $0.01202 |
| Sonnet 5 | $0.00481 | $0.00481 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade C, and why
htmx scanned grade C 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 3d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Entire post re-rendered --> How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
htmx Best Practices
This document outlines the definitive best practices for utilizing htmx within our projects. Adhering to these guidelines ensures maintainable, performant, and secure applications.
1. Code Organization and Structure
Always structure your HTML with htmx attributes as the primary driver for interactivity. Keep JavaScript minimal and reserved for complex, client-side-only interactions.
1.1 Modular HTML Fragments
Design your server-side templates to return small, self-contained HTML fragments. This keeps responses lean and promotes reusability.
❌ BAD: Returning a full page for a small update.
<!-- Server response for a "like" action -->
<html>
<head>...</head>
<body>
<header>...</header>
<main>
<div id="post-123">
<!-- Entire post re-rendered -->
<button hx-post="/like/123" hx-target="#post-123" hx-swap="outerHTML">
Like (10)
</button>
</div>
</main>
<footer>...</footer>
</body>
</html>
✅ GOOD: Returning only the updated component.
<!-- Server response for a "like" action -->
<button hx-post="/like/123" hx-target="#like-button-123" hx-swap="outerHTML">
Unlike (11)
</button>
<!-- Initial HTML -->
<div id="post-123">
<button id="like-button-123" hx-post="/like/123" hx-target="#like-button-123" hx-swap="outerHTML">
Like (10)
</button>
</div>
1.2 Attribute Placement and Inheritance
Place hx-* attributes on the element that triggers the action or on a parent element for inheritance. This improves readability and reduces repetition.
❌ BAD: Repeating attributes unnecessarily.
<div class="item">
<button hx-post="/delete/1" hx-target="#item-1" hx-swap="outerHTML">Delete</button>
</div>
<div class="item">
<button hx-post="/delete/2" hx-target="#item-2" hx-swap="outerHTML">Delete</button>
</div>
✅ GOOD: Leveraging attribute inheritance.
<div hx-target="closest .item" hx-swap="outerHTML">
<div id="item-1" class="item">
<button hx-post="/delete/1">Delete</button>
</div>
<div id="item-2" class="item">
<button hx-post="/delete/2">Delete</button>
</div>
</div>
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.
- 3d ago First seen · 257 lines · 2,404 tokens per session scan C 23ac0d777564
htmx 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,404 tokens to every session, about $0.0120 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
jawn
Cursor rule "jawn" from Helicone/helicone, covering helicone jawn controller and tanstack query integration, controller pattern, manager pattern, frontend hooks with tanstack query and type definitions.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
react-query-cursorrules-prompt-file
Cursor rules for React development with React Query integration.
next-js-server-actions
A guide for Next.js server actions, which let server-side code handle requests from an application interface, with validation and structured error responses.
data-fetching-rules-for-server-components
A set of rules for fetching data inside Next.js 14 server components, which render on the server rather than in the browser.
middleware
When you need create a middleware to protect some page of Next.js app.