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/floriscornel/todo-mcpWrote 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/floriscornel/todo-mcp/database-patterns)<a href="https://agentmods.dev/rules/floriscornel/todo-mcp/database-patterns"><img src="https://agentmods.dev/badge/rules/floriscornel/todo-mcp/database-patterns/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/floriscornel/todo-mcp/database-patterns"><img src="https://agentmods.dev/badge/rules/floriscornel/todo-mcp/database-patterns.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.00316 | $0.00316 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
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 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 Development Patterns
Schema Changes
When modifying src/db/schema.ts:
-
Update Schema First:
- Modify tables in
schema.ts - Update Zod validation schemas accordingly
- Ensure type safety between database and validation
- Modify tables in
-
Generate Migration:
npm run db:generate -
Test Migration:
- Apply to development database:
npm run db:migrate - Verify migration works with test database
- Check that rollback is possible if needed
- Apply to development database:
Database Operations
- Use the
todoDbinterface fromsrc/db/index.ts - All database operations should be type-safe with Drizzle
- Use transactions for operations that modify multiple tables
- Handle database errors gracefully with proper error types
Schema Patterns
- Use
generatedAlwaysAsIdentity()for primary keys - Include
createdAttimestamp withdefaultNow() - Use appropriate varchar lengths based on UI constraints
- Foreign keys should have proper references with cascade rules
Migration Best Practices
- Keep migrations focused and atomic
- Test migrations with real data scenarios
- Include both up and down migrations when possible
- Document complex migrations with comments
Connection Management
- Use environment variables for database URLs
- Separate test and development databases
- Connection pooling is handled by the postgres library
- Always close connections in tests
@src/db/schema.ts @src/db/postgres.ts
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 · 52 lines · 316 tokens per session scan A d7f9e5fcfd3d
database-patterns is a cursor rule published in the GitHub repository floriscornel/todo-mcp (2 stars, last pushed 8mo ago), licensed MIT. It adds 316 tokens to every session, about $0.0013 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.