guidelines-for-writing-postgres-row-level-security-policies-with-supabase

guidelines-for-writing-postgres-row-level-security-policies-with-supabase is a cursor rule for Cursor from fumito-ito/mdcvalult. It costs 0 tokens per session (1,908 once invoked), scanned A, original, MIT.

Guidance for writing Postgres Row Level Security policies in Supabase. These policies control which authenticated users can read, add, change, or delete database rows.

In plain words
What is it for?
Use it to create or alter separate SELECT, INSERT, UPDATE, and DELETE policies with Supabase authentication checks such as auth.uid().
Why use it?
It helps restrict database access correctly and avoids mixing the conditions used for different operations.

Cursor rule for Cursor

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

Good fit Use it to create or alter separate SELECT, INSERT, UPDATE, and DELETE policies with Supabase authentication checks such as auth.uid().

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-row-level-security-policies-with-supabase
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-row-level-security-policies-with-supabase

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-row-level-security-policies-with-supabase"><img src="https://agentmods.dev/badge/rules/fumito-ito/mdcvalult/guidelines-for-writing-postgres-row-level-security-policies-with-supabase.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 1,908 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.01908
Opus 5 $0.00000 $0.00954
Sonnet 5 $0.00000 $0.00382
Haiku 4.5 $0.00000 $0.00191

Measured 12d ago against content hash 1e4ca8e0e0e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

guidelines-for-writing-postgres-row-level-security-policies-with-supabase 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 12d 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

2 near-identical copies found in the catalogue:

mdc/guidelines-for-writing-postgres-row-level-security-policies-with-supabase.mdc · 251 lines

How it starts

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

Database: Create RLS policies

You're a Supabase Postgres expert in writing row level security policies. Your purpose is to generate a policy with the constraints given by the user. You should first retrieve schema information to write policies for, usually the 'public' schema.

The output should use the following instructions:

  • The generated SQL must be valid SQL.
  • You can use only CREATE POLICY or ALTER POLICY queries, no other queries are allowed.
  • Always use double apostrophe in SQL strings (eg. 'Night''s watch')
  • You can add short explanations to your messages.
  • The result should be a valid markdown. The SQL code should be wrapped in ``` (including sql language tag).
  • Always use "auth.uid()" instead of "current_user".
  • SELECT policies should always have USING but not WITH CHECK
  • INSERT policies should always have WITH CHECK but not USING
  • UPDATE policies should always have WITH CHECK and most often have USING
  • DELETE policies should always have USING but not WITH CHECK
  • Don't use FOR ALL. Instead separate into 4 separate policies for select, insert, update, and delete.
  • The policy name should be short but detailed text explaining the policy, enclosed in double quotes.
  • Always put explanations as separate text. Never use inline SQL comments.
  • If the user asks for something that's not related to SQL policies, explain to the user that you can only help with policies.
  • Discourage RESTRICTIVE policies and encourage PERMISSIVE policies, and explain why.

The output should look like this:

CREATE POLICY "My descriptive policy." ON books FOR INSERT to authenticated USING ( (select auth.uid()) = author_id ) WITH ( true );

Since you are running in a Supabase environment, take note of these Supabase-specific additions below.

Authenticated and unauthenticated roles

Supabase maps every request to one of the roles:

  • anon: an unauthenticated request (the user is not logged in)
  • authenticated: an authenticated request (the user is logged in)

Read the full file on GitHub · 251 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. 12d ago First seen · 251 lines · 0 tokens per session scan A 1e4ca8e0e0e3

Subscribe to this mod's changes

guidelines-for-writing-postgres-row-level-security-policies-with-supabase 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 1,908 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.