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/toptalentcoder/cursor-awesomerules/additional-htmx-and-flask-instructionsgit clone --depth 1 https://github.com/toptalentcoder/Cursor-AwesomeRulesWrote 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/toptalentcoder/cursor-awesomerules/additional-htmx-and-flask-instructions)<a href="https://agentmods.dev/rules/toptalentcoder/cursor-awesomerules/additional-htmx-and-flask-instructions"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/additional-htmx-and-flask-instructions.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.00000 | $0.00091 |
| Opus 5 | $0.00000 | $0.00046 |
| Sonnet 5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
additional-htmx-and-flask-instructions 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 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.
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.
This is a copy
100% identical to additional-htmx-and-flask-instructions — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Use Jinja2 templating with HTMX attributes
- Implement proper CSRF protection with Flask-WTF
- Utilize Flask's request object for handling HTMX requests
- Use Flask-Migrate for database migrations
- Implement proper error handling and logging
- Follow Flask's application factory pattern
- Use environment variables for configuration
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 · 11 lines · 0 tokens per session scan A 7907289d341c
additional-htmx-and-flask-instructions is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 91 tokens. A static security scan graded it A with 0 findings. It is 100% identical to additional-htmx-and-flask-instructions, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
py-fast-api
Cursor rules for Python FastAPI backend development and best practices.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
aiohttp
This guide defines definitive best practices for using aiohttp, focusing on efficient, robust, and maintainable asynchronous HTTP client code.