django-python-cursor-rules

A set of coding rules for Python backend projects built with Django, a Python web framework. It provides general guidance for writing Django and Python server-side code.

In plain words
What is it for?
Use it when creating, changing, or reviewing Django views, models, services, and other Python backend code.
Why use it?
It helps keep backend code consistent with the technologies and conventions used by the project.

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/tacc/hpcperfstats/django-python-cursor-rules
Clone the repo
git clone --depth 1 https://github.com/TACC/HPCPerfStats
Per session 1,088 This file is loaded in full into every session.
When invoked 1,088 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.01088 $0.01088
Opus 5 $0.00544 $0.00544
Sonnet 5 $0.00218 $0.00218
Haiku 4.5 $0.00109 $0.00109

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

Security

Grade A, and why

django-python-cursor-rules 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 2d 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.

hpcperfstats/cursor-rules/django-python-cursor-rules.mdc · 68 lines

The source is not reproduced here

Licensed LGPL-2.1

The repository is licensed LGPL-2.1, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 68 lines · 1,088 tokens per session scan A a1464eacdf09

Subscribe to this mod's changes

django-python-cursor-rules is a cursor rule published in the GitHub repository TACC/HPCPerfStats (58 stars, last pushed 2d ago), licensed LGPL-2.1. It adds 1,088 tokens to every session, about $0.0054 per session on Opus 5. 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.