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/oakensoul/nextjs-cursor-prompts/database-safegit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/database-safe)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/database-safe"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/database-safe.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.00000 | $0.02022 |
| Opus 5 | $0.00000 | $0.01011 |
| Sonnet 5 | $0.00000 | $0.00404 |
| Haiku 4.5 | $0.00000 | $0.00202 |
Grade A, and why
database-safe 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Safety Rule
This rule enforces safe practices for database operations that could cause data loss, corruption, or application downtime.
🎯 DATABASE SAFETY PRINCIPLES:
- BACKUP FIRST - Always have a recovery plan
- TEST MIGRATIONS - Verify on non-production data
- ROLLBACK READY - Ensure reversible operations
- VALIDATE CONSTRAINTS - Check data integrity
- MONITOR PERFORMANCE - Watch for blocking operations
🚫 FORBIDDEN ACTIONS:
- DO NOT modify production database without tested migration
- DO NOT drop columns or tables without explicit backup verification
- DO NOT run migrations during peak traffic hours
- DO NOT ignore foreign key constraints or data relationships
- DO NOT use raw SQL without parameterized queries
- DO NOT modify schema without updating application code
- DO NOT skip migration testing on realistic data volumes
- DO NOT create migrations that lock tables for extended periods
✅ REQUIRED SAFETY MEASURES:
🔒 SECURITY REQUIREMENTS:
- Use parameterized queries - prevent SQL injection attacks
- Validate all inputs - sanitize user data before database operations
- Implement proper permissions - least privilege access for database users
- Audit sensitive operations - log data access and modifications
- Encrypt sensitive data - protect PII and financial information
🔄 MIGRATION REQUIREMENTS:
- Write reversible migrations - provide both up and down migrations
- Test on realistic data - verify with production-sized datasets
- Check for blocking operations - avoid long-running locks
- Validate data integrity - ensure referential integrity after migration
- Document breaking changes - explain impact on application code
📊 PERFORMANCE REQUIREMENTS:
- Index new columns - ensure queries remain performant
- Monitor query performance - watch for N+1 queries and slow operations
- Use connection pooling - prevent connection exhaustion
- Implement timeouts - avoid hanging database connections
- Batch large operations - process bulk changes in chunks
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 · 263 lines · 0 tokens per session scan A b93a73724c78
database-safe is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,022 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
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
database
Database rules — apply when working with database schemas, queries, migrations, or ORM models.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.