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/ofershap/drizzle-best-practices/best-practicesgit clone --depth 1 https://github.com/ofershap/drizzle-best-practicesWrote 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/ofershap/drizzle-best-practices/best-practices)<a href="https://agentmods.dev/rules/ofershap/drizzle-best-practices/best-practices"><img src="https://agentmods.dev/badge/rules/ofershap/drizzle-best-practices/best-practices.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 | $0.00114 | $0.00114 |
| Opus 5 | $0.00057 | $0.00057 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
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 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.
What it actually says
- Use Drizzle schema definition (pgTable/mysqlTable/sqliteTable) - never write Prisma-style schema files
- Use $inferSelect and $inferInsert for type inference - never manually define types that mirror DB schemas
- Use the Drizzle query builder API - never use raw SQL strings unless absolutely necessary
- Use drizzle-kit for migrations - never write migration SQL manually
- Use prepared statements for queries that run frequently
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 · 114 tokens per session scan A ae466df587da
best-practices is a cursor rule published in the GitHub repository ofershap/drizzle-best-practices (0 stars, last pushed 6mo ago), licensed MIT. It adds 114 tokens to every session, about $0.0006 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-31.
Other cursor rules, from other repositories
cursorrules
// ✅ Correct import { Model } from '@eloquentjs/core' import { v } from '@eloquentjs/validator' import User from './models/User.js'.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
architecture
FastAPI layer architecture rules — Router → Service → Repository with Protocol injection.
prisma
Prisma database patterns and conventions for Next.js and TypeScript projects.
sqlalchemy
SQLAlchemy database patterns and conventions.
best-practices
Tailwind CSS Best Practices - enforces v4 syntax and CSS-first config when working with Tailwind code.