django

Rules for Django, a Python web framework for building websites and back-end services. They cover models, the database interface, forms, authentication, settings, and efficient related-data queries.

In plain words
What is it for?
Use them when creating or reviewing Django apps, database models, admin pages, forms, authentication, configuration, and ORM queries.
Why use it?
They encourage common Django patterns and help avoid slow database access, unsafe settings, and duplicated application structure.

Cursor rule for Cursor

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/wangtingyeye/llm-agent-study/django
Clone the repo
git clone --depth 1 https://github.com/WangTingYeYe/llm-agent-study

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 261 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.00261
Opus 5 $0.00000 $0.00130
Sonnet 5 $0.00000 $0.00052
Haiku 4.5 $0.00000 $0.00026

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

Security

Grade A, and why

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

.cursor/rules/frameworks/django.mdc · 43 lines

What it actually says


description: 该规则解释了 Django 后端开发的约定和最佳实践。 globs: **/*.py alwaysApply: false

Django 规则

  • 使用 python manage.py startapp 在项目中创建新应用
  • models.py 中保存模型,并在 admin.py 中注册以使用管理界面
  • 使用 Django 的 ORM 而非原始 SQL 查询
  • 使用 select_relatedprefetch_related 避免 N+1 查询问题:
# 良好模式
users = User.objects.select_related('profile')
posts = Post.objects.prefetch_related('tags')
  • 使用 Django 表单进行验证:
class UserForm(forms.ModelForm):
    class Meta:
        model = User
        fields = ['username', 'email']
  • 为常见查询创建自定义模型管理器:
class ActiveUserManager(models.Manager):
    def get_queryset(self):
        return super().get_queryset().filter(is_active=True)
  • 使用 Django 内置的身份验证系统
  • 在环境变量中存储设置并通过 settings.py 访问
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 · 43 lines · 0 tokens per session scan A 173cd8555b93

Subscribe to this mod's changes

django is a cursor rule published in the GitHub repository WangTingYeYe/llm-agent-study (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 261 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-31.