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.
git clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rulesWrote 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/paulpham157/paul-s-cursor-rules/django-orm-for-database-operations)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/django-orm-for-database-operations"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/django-orm-for-database-operations.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.00048 |
| Opus 5 | $0.00000 | $0.00024 |
| Sonnet 5 | $0.00000 | $0.00010 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
django-orm-for-database-operations 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- django-orm-for-database-operations — 100% identical, 0 lines differ
- django-orm-for-database-operations — 100% identical, 0 lines differ
What it actually says
description: Specifies that Django's ORM should be used for interacting with the database when defining models. This encourages a consistent approach to database operations across the project. globs: **/models.py
- Implement Django ORM for database operations
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 · 5 lines · 48 tokens per session scan A db5ad2792a11
django-orm-for-database-operations 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 48 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.
Other cursor rules, from other repositories
java-springboot-jpa-cursorrules-prompt-file
Cursor rules for Java development with Springboot and JPA integration.
nodejs-mongodb-cursorrules-prompt-file-tutorial
Cursor rules for Node.js development with MongoDB integration.
nodejs-mongodb-jwt-express-react-cursorrules-promp
Cursor rules for Node.js development with MongoDB, JWT, Express, and React integration.
supabase
Supabase: RLS, edge functions, realtime.
prisma
Prisma: schema modeling, queries, migrations.
convex
Convex: real-time backend, queries, mutations, schema.