htmx

A set of rules for HTMX, a tool that lets HTML trigger server requests and update parts of a page without a full reload.

In plain words
What is it for?
Use it when adding buttons, forms, or other page elements that load or submit data, handle events, and replace selected parts of a web page.
Why use it?
It reduces guesswork about which HTMX attributes to use, where responses should appear, and how page updates should work.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/chand1012/cursorrules/htmx
Clone the repo
git clone --depth 1 https://github.com/chand1012/cursorrules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01881
Opus 5 $0.00000 $0.00941
Sonnet 5 $0.00000 $0.00376
Haiku 4.5 $0.00000 $0.00188

Measured yesterday against content hash d971db1e17ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

frameworks/htmx.mdc · 171 lines

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-get for read operations and hx-post for write operations to align with RESTful conventions.
  • Specify hx-target with CSS selectors (e.g., #result) to control where server responses are inserted in the DOM.
  • Leverage hx-swap to define how content is updated (e.g., innerHTML for replacing content inside an element, outerHTML for replacing the element itself, beforebegin or afterend for positioning relative to the target).
  • Use hx-select to 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-trigger to specify when actions occur (e.g., click, load, every 1s for polling).
  • Combine multiple triggers with commas (e.g., hx-trigger="click, keyup") for flexible event handling.
  • Utilize hx-on to 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.

Read the full file on GitHub · 171 lines

Changes

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.

  1. yesterday First seen · 171 lines · 1,881 tokens per session scan A d971db1e17ed

Subscribe to this mod's changes

htmx is a cursor rule published in the GitHub repository chand1012/cursorrules (13 stars, last pushed 9mo 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.