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/shumatsumonobu/awesome-ai-rules/databasegit clone --depth 1 https://github.com/shumatsumonobu/awesome-ai-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/shumatsumonobu/awesome-ai-rules/database)<a href="https://agentmods.dev/rules/shumatsumonobu/awesome-ai-rules/database"><img src="https://agentmods.dev/badge/rules/shumatsumonobu/awesome-ai-rules/database.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.00249 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
database 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 5d 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
Database Rules (auto-attached to packages/api/)
Auto-attached when editing any .ts file under packages/api/. This means database rules never contaminate frontend code -- if you're editing a React component, this file isn't loaded.
Drizzle Conventions
- Define tables in
src/schema/, one file per table. - Use
drizzle-kitfor migrations. Never write migration SQL by hand. - Use the query builder. Raw SQL only for performance-critical paths with a justifying comment.
Patterns
export const users = pgTable("users", {
id: uuid("id").defaultRandom().primaryKey(),
email: text("email").notNull().unique(),
createdAt: timestamp("created_at").defaultNow().notNull(),
});
- Services return plain objects, never Drizzle row types.
- Wrap multi-table writes in transactions.
- Add indexes for columns used in WHERE and JOIN.
Boundary
The web package never imports drizzle-orm. All DB access goes through this package's service layer.
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.
- 5d ago First seen · 35 lines · 0 tokens per session scan A 75e6e2a3fd54
database is a cursor rule published in the GitHub repository shumatsumonobu/awesome-ai-rules (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 249 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.
Other cursor rules, from other repositories
snowflake-data-engineering-cursorrules-prompt-file
Cursor rules for Snowflake SQL, data pipelines (Dynamic Tables, Streams, Tasks, Snowpipe), semi-structured data, Snowflake Postgres, and cost optimization.
snowflake-snowpark-dbt-cursorrules-prompt-file
Cursor rules for Snowpark Python (DataFrames, UDFs, stored procedures) and dbt with the Snowflake adapter.
java-springboot-jpa-cursorrules-prompt-file
Cursor rules for Java development with Springboot and JPA integration.
database
Database best practices focusing on Prisma and Supabase integration.
nodejs-mongodb-cursorrules-prompt-file-tutorial
Cursor rules for Node.js development with MongoDB integration.
postgresql
PostgreSQL production rules. Safe migrations, parameterized queries, TIMESTAMPTZ, proper indexing strategy.