htmx-and-flask-best-practices

htmx-and-flask-best-practices is a cursor rule for Cursor from paulpham157/paul-s-cursor-rules. It costs 0 tokens per session (81 once invoked), scanned A, original, MIT.

A set of coding rules for building HTMX interfaces with Flask, a Python web framework, including server-rendered pages, forms, URLs, JSON responses, and database access.

In plain words
What is it for?
Use it when developing Flask applications that update pages with HTMX requests and need modular routes, protected forms, and database support.
Why use it?
It keeps common Flask and HTMX decisions consistent and reduces mistakes when handling forms, routes, templates, and data.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when developing Flask applications that update pages with HTMX requests and need modular routes, protected forms, and database support.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices
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.

Clone the repo
git clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rules

Made for: Cursor.

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

agentmods badge for htmx-and-flask-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices/github.svg)](https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices)
Your own site
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices/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.

agentmods 80×15 button for htmx-and-flask-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/htmx-and-flask-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 81 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00081
Opus 5 $0.00000 $0.00041
Sonnet 5 $0.00000 $0.00016
Haiku 4.5 $0.00000 $0.00008

Measured 6d ago against content hash f1d77d4ce9c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

htmx-and-flask-best-practices 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

1/framework_rules/rules/htmx-flask-cursorrules-prompt-file/htmx-and-flask-best-practices.mdc · 10 lines

What it actually says

  • Use Flask's render_template for server-side rendering
  • Implement Flask-WTF for form handling
  • Utilize Flask's url_for for generating URLs
  • Use Flask's jsonify for JSON responses
  • Implement Flask-SQLAlchemy for database operations
  • Utilize Flask's Blueprint for modular applications
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. 6d ago First seen · 10 lines · 0 tokens per session scan A f1d77d4ce9c8

Subscribe to this mod's changes

htmx-and-flask-best-practices is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 81 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-09-03.