database

database is a cursor rule for Cursor from ItamarZand88/awesome-agent-conventions. It costs 444 tokens per session, scanned A, a copy of database, MIT.

A set of database guidelines focused on Prisma and Supabase. Prisma is a tool for working with databases from application code, while Supabase provides database, authentication, storage, and access-control services.

In plain words
What is it for?
Use it when configuring Prisma or Supabase, defining models and relations, writing queries, adding migrations and indexes, or setting authentication and row-level security.
Why use it?
It helps developers structure database models, queries, security rules, and setup consistently.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when configuring Prisma or Supabase, defining models and relations, writing queries, adding migrations and indexes, or setting authentication and row-level security.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/itamarzand88/awesome-agent-conventions/database
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.

Clone the repo
git clone --depth 1 https://github.com/ItamarZand88/awesome-agent-conventions

Made for: Cursor.

Wrote 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.

agentmods badge for database

README.md
[![agentmods](https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/database/github.svg)](https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/database)
Your own site
<a href="https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/database"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/database/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.

agentmods 80×15 button for database

Your own site · 80×15
<a href="https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/database"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/database.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 444 This file is loaded in full into every session.
When invoked 444 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod 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.1 $0.00444 $0.00444
Opus 5.5 $0.00178 $0.00178
Sonnet 5.5 $0.00089 $0.00089
Haiku 4.5 $0.00044 $0.00044

Measured 1mo ago against content hash 2198e84e7332, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

This is a copy

89% identical to database — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

conventions/agent-rules/examples/awesome-cursorrules-database/database.mdc · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.


description: "Database best practices focusing on Prisma and Supabase integration" globs: prisma//*, src/db//, **/.prisma, supabase/**/* alwaysApply: false

Database Best Practices

Prisma Setup

  • Use proper schema design
  • Implement proper migrations
  • Use proper relation definitions
  • Configure proper connection
  • Implement proper seeding
  • Use proper client setup

Prisma Models

  • Use proper model naming
  • Implement proper relations
  • Use proper field types
  • Define proper indexes
  • Implement proper constraints
  • Use proper enums

Prisma Queries

  • Use proper query optimization
  • Implement proper filtering
  • Use proper relations loading
  • Handle transactions properly
  • Implement proper pagination
  • Use proper aggregations

Supabase Setup

  • Configure proper project setup
  • Implement proper authentication
  • Use proper database setup
  • Configure proper storage
  • Implement proper policies
  • Use proper client setup

Supabase Security

  • Implement proper RLS policies
  • Use proper authentication
  • Configure proper permissions
  • Handle sensitive data properly
  • Implement proper backups
  • Use proper encryption

Supabase Queries

  • Use proper query optimization
  • Implement proper filtering
  • Use proper joins
  • Handle real-time properly
  • Implement proper pagination
  • Use proper functions

Database Design

  • Use proper normalization
  • Implement proper indexing
  • Use proper constraints
  • Define proper relations
  • Implement proper cascades
  • Use proper data types

Performance

  • Use proper connection pooling
  • Implement proper caching
  • Use proper query optimization
  • Handle N+1 queries properly
  • Implement proper batching
  • Monitor performance metrics

Security

  • Use proper authentication
  • Implement proper authorization
  • Handle sensitive data properly
  • Use proper encryption
  • Implement proper backups
  • Monitor security issues

Read the full file on GitHub · 88 lines

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. 1mo ago First seen · 88 lines · 444 tokens per session scan A 2198e84e7332

Subscribe to this mod's changes

database is a cursor rule published in the GitHub repository ItamarZand88/awesome-agent-conventions (34 stars, last pushed 2mo ago), licensed MIT. It adds 444 tokens to every session, about $0.0018 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to database, differing in 1 line, and is treated as a copy.