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/aiagentwithdhruv/ai-dev-stackWrote 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/aiagentwithdhruv/ai-dev-stack/30-database-postgres)<a href="https://agentmods.dev/rules/aiagentwithdhruv/ai-dev-stack/30-database-postgres"><img src="https://agentmods.dev/badge/rules/aiagentwithdhruv/ai-dev-stack/30-database-postgres/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/aiagentwithdhruv/ai-dev-stack/30-database-postgres"><img src="https://agentmods.dev/badge/rules/aiagentwithdhruv/ai-dev-stack/30-database-postgres.svg" alt="Reviewed on agentmods" width="80" 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.00252 |
| Opus 5.5 | $0.00000 | $0.00101 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
30-database-postgres 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 1mo 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:
- PostgreSQL is the source of truth for structured application data.
- Use migrations for all schema changes.
- Design tables with clear ownership, timestamps, and constraints.
- Add indexes for common filters and joins.
- Use foreign keys where appropriate.
- Prefer soft-delete only when there is a real product need.
Schema design expectations:
- Every core entity should have:
- id
- created_at
- updated_at
- For SaaS systems, include tenant/organization isolation where relevant.
- Use enums or constrained fields for finite states where appropriate.
- Keep schemas normalized unless denormalization is justified by performance needs.
Repository rules:
- All DB access must go through repositories/data access layer.
- Keep query code out of routes and services unless trivial and already patterned.
- Parameterize queries.
- Avoid N+1 query patterns.
- Use transactions when multiple writes must succeed together.
Do not:
- Write raw SQL inside controllers/routes.
- Make schema changes without migration files.
- Assume single-tenant if the product is multi-tenant.
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.
- 1mo ago First seen · 34 lines · 0 tokens per session scan A 90563edfc528
30-database-postgres is a cursor rule published in the GitHub repository aiagentwithdhruv/ai-dev-stack (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 252 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
postgresql
PostgreSQL: advanced SQL, performance, extensions.
supabase-db-rls
Guidelines for writing Postgres Row Level Security policies.
supabase-db-create-functions
Guidelines for writing Supabase database functions.
supabase-db-styleguide
Guidelines for writing Postgres SQL.
supabase-db-create-migrations
Guidelines for writing Postgres SQL.
postgres
Postgres roof: parameterized SQL, forward-only migrations, measured indexes. Index only.