004-database-patterns

Rules for a database schema stored in src/db/schema.ts, using Drizzle ORM with Cloudflare D1. Drizzle ORM is a tool for working with databases from code, while migrations record database structure changes.

In plain words
What is it for?
Use them when editing the schema, inserting or updating records, or creating database migrations for Cloudflare D1.
Why use it?
They prevent unsupported database transactions and incorrect ID handling. They also ensure schema changes use the project’s required migration-generation process.

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/passionmuse16/food-tracker/004-database-patterns
Clone the repo
git clone --depth 1 https://github.com/passionmuse16/food-tracker

Made for: Cursor.

Per session 136 This file is loaded in full into every session.
When invoked 136 The same file — it is already loaded in full.
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.00136 $0.00136
Opus 5 $0.00068 $0.00068
Sonnet 5 $0.00027 $0.00027
Haiku 4.5 $0.00014 $0.00014

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

Security

Grade A, and why

004-database-patterns 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/004-database-patterns.mdc · 19 lines

What it actually says

Database Patterns

The database schema is in src/db/schema.ts.

Drizzle ORM Guidelines

  • Never use Drizzle ORM Transactions since Cloudflare D1 doesn't support them.
  • When inserting or updating items with Drizzle ORM never pass an id since we autogenerate it in the schema.
  • When using db.insert().values() never pass and id because we autogenerate them.

Migration Workflow

Never generate SQL migration files. Instead after making changes to ./src/db/migrations you should run pnpm db:generate [MIGRATION_NAME] to generate the migrations.

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 · 19 lines · 136 tokens per session scan A ebc699be742a

Subscribe to this mod's changes

004-database-patterns is a cursor rule published in the GitHub repository passionmuse16/food-tracker (2 stars, last pushed 10mo ago), licensed MIT. It adds 136 tokens to every session, about $0.0007 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.