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/chand1012/cursorrulesWrote 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/chand1012/cursorrules/htmx)<a href="https://agentmods.dev/rules/chand1012/cursorrules/htmx"><img src="https://agentmods.dev/badge/rules/chand1012/cursorrules/htmx/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/chand1012/cursorrules/htmx"><img src="https://agentmods.dev/badge/rules/chand1012/cursorrules/htmx.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01881 |
| Opus 5.5 | $0.00000 | $0.00752 |
| Sonnet 5.5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
htmx 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 1mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTMX Development Best Practices
HTML Structure and HTMX Attributes
HTMX enhances HTML by adding attributes that trigger dynamic behaviors, such as AJAX requests and content updates. Proper use of these attributes is foundational to effective HTMX development.
- Use
hx-getfor read operations andhx-postfor write operations to align with RESTful conventions. - Specify
hx-targetwith CSS selectors (e.g.,#result) to control where server responses are inserted in the DOM. - Leverage
hx-swapto define how content is updated (e.g.,innerHTMLfor replacing content inside an element,outerHTMLfor replacing the element itself,beforebeginorafterendfor positioning relative to the target). - Use
hx-selectto extract specific portions of a server response, reducing unnecessary DOM updates. - Minimize attribute clutter by grouping related functionality on parent elements where possible.
Example:
<button hx-get="/api/users" hx-target="#user-list" hx-swap="innerHTML">
Load Users
</button>
<div id="user-list"></div>
Event Handling
HTMX uses events to trigger actions, making event handling a core part of its workflow.
- Use
hx-triggerto specify when actions occur (e.g.,click,load,every 1sfor polling). - Combine multiple triggers with commas (e.g.,
hx-trigger="click, keyup") for flexible event handling. - Utilize
hx-onto attach custom JavaScript event handlers directly in HTML (e.g.,hx-on:click="console.log('Clicked!')"). - Leverage custom events (e.g.,
htmx:afterSwap) for complex interactions, triggered via HTMX’s event system. - Debounce or throttle events using modifiers like
hx-trigger="keyup delay:500ms"to prevent excessive requests.
Example:
<input hx-post="/search" hx-trigger="keyup delay:300ms" hx-target="#results" />
<div id="results"></div>
Forms and Validation
HTMX simplifies form handling by enabling AJAX submissions, but validation remains critical.
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.
- 1mo ago First seen · 171 lines · 1,881 tokens per session scan A d971db1e17ed
htmx is a cursor rule published in the GitHub repository chand1012/cursorrules (14 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,881 tokens. 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
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.