agentmods.dev

guidelines-for-writing-postgres-migrations-with-supabase-cli

guidelines-for-writing-postgres-migrations-with-supabase-cli is a cursor rule for Cursor from fumito-ito/mdcvalult. It costs 0 tokens per session (552 once invoked), scanned A, original, MIT.

A set of rules for creating PostgreSQL database migration files for projects using the Supabase command-line tool. A migration is a tracked database change, such as creating a table or changing a column.

In plain words
What is it for?
Use it when writing SQL changes in `supabase/migrations/`, including the required UTC timestamp filename and migration comments.
Why use it?
It keeps database changes ordered, documented, and compatible with the project’s migration process.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

not rated 33repo 1y ago A scan 0 tokens original MIT

Good fit Use it when writing SQL changes in supabase/migrations/, including the required UTC timestamp filename and migration comments.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli
View source ↗ fumito-ito/mdcvalult
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/fumito-ito/mdcvalult

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 guidelines-for-writing-postgres-migrations-with-supabase-cli

README.md
[![agentmods](https://agentmods.dev/badge/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli/github.svg)](https://agentmods.dev/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli)
Your own site
<a href="https://agentmods.dev/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli"><img src="https://agentmods.dev/badge/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli/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 guidelines-for-writing-postgres-migrations-with-supabase-cli

Your own site · 80×15
<a href="https://agentmods.dev/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli"><img src="https://agentmods.dev/badge/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-migrations-with-supabase-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 552 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00000 $0.00552
Opus 5.5 $0.00000 $0.00221
Sonnet 5.5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

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

Security

Grade A, and why

guidelines-for-writing-postgres-migrations-with-supabase-cli 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 2mo 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

Copies of this mod

3 near-identical copies found in the catalogue:

mdc/guidelines-for-writing-postgres-migrations-with-supabase-cli.mdc · 53 lines

How it starts

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

Database: Create migration

You are a Postgres Expert who loves creating secure database schemas.

This project uses the migrations provided by the Supabase CLI.

Creating a migration file

Given the context of the user's message, create a database migration file inside the folder supabase/migrations/.

The file MUST following this naming convention:

The file MUST be named in the format YYYYMMDDHHmmss_short_description.sql with proper casing for months, minutes, and seconds in UTC time:

  1. YYYY - Four digits for the year (e.g., 2024).
  2. MM - Two digits for the month (01 to 12).
  3. DD - Two digits for the day of the month (01 to 31).
  4. HH - Two digits for the hour in 24-hour format (00 to 23).
  5. mm - Two digits for the minute (00 to 59).
  6. ss - Two digits for the second (00 to 59).
  7. Add an appropriate description for the migration.

For example:

20240906123045_create_profiles.sql

SQL Guidelines

Write Postgres-compatible SQL code for Supabase migration files that:

  • Includes a header comment with metadata about the migration, such as the purpose, affected tables/columns, and any special considerations.
  • Includes thorough comments explaining the purpose and expected behavior of each migration step.
  • Write all SQL in lowercase.
  • Add copious comments for any destructive SQL commands, including truncating, dropping, or column alterations.
  • When creating a new table, you MUST enable Row Level Security (RLS) even if the table is intended for public access.
  • When creating RLS Policies
    • Ensure the policies cover all relevant access scenarios (e.g. select, insert, update, delete) based on the table's purpose and data sensitivity.
    • If the table is intended for public access the policy can simply return true.
    • RLS Policies should be granular: one policy for select, one for insert etc) and for each supabase role (anon and authenticated). DO NOT combine Policies even if the functionality is the same for both roles.
    • Include comments explaining the rationale and intended behavior of each security policy

Read the full file on GitHub · 53 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. 2mo ago First seen · 53 lines · 0 tokens per session scan A aa844e4fd5de

Subscribe to this mod's changes

guidelines-for-writing-postgres-migrations-with-supabase-cli is a cursor rule published in the GitHub repository fumito-ito/mdcvalult (33 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 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-30.

DatabasesPostgreSQL
Related

guidelines-for-writing-postgres-migrations-with-supabase-cli compared with cursor rules from other repositories

guidelines-for-writing-postgres-migrations-with-supabase-cli next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
guidelines-for-writing-postgres-migrations-with-supabase-clifumito-ito/mdcvalultCursor rule331y agoMITA0Cursor
adapter-featuresprest/prestCursor rule4.6ktodayMITA773Cursor
unit-tests-tddprest/prestCursor rule4.6ktodayMITA375Cursor
planning-and-delegationprest/prestCursor rule4.6ktodayMITA912Cursor
integration-testsprest/prestCursor rule4.6ktodayMITA0Cursor
postgresqlPatrickJS/awesome-cursorrulesCursor rule41k5mo agoCC0-1.0A318Cursor
netlify-database-migration-from-extensionnetlify/context-and-toolsCursor rule51yesterdayMITA16Cursor