65-stack-supabase

A set of coding rules for Supabase, a backend platform, covering database access controls, user sign-in, and server functions.

In plain words
What is it for?
Use it when building or reviewing Supabase tables, Row-Level Security policies, authentication, or Edge Functions.
Why use it?
It helps prevent security mistakes such as exposing database rows, trusting unsafe browser state, or running slow access checks.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/zoxknez/ai-coding-rules/65-stack-supabase
Clone the repo
git clone --depth 1 https://github.com/zoxknez/ai-coding-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 934 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00934
Opus 5 $0.00000 $0.00467
Sonnet 5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00093

Measured 2d ago against content hash a70541923785, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

65-stack-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 2d 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

1 near-identical copy found in the catalogue:

.cursor/rules/65-stack-supabase.mdc · 163 lines

How it starts

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

Supabase Stack Rules

Row-Level Security (RLS)

Mandatory Practices

  • Enable RLS on ALL tables (no exceptions)
  • Use (SELECT auth.uid()) pattern for performance (17x faster)
  • Index all columns used in RLS policies
  • Always guard against null auth state

Performance Patterns

Function Caching (CRITICAL)
-- ❌ BAD: O(N × f(C)) — function per row
auth.uid() = user_id

-- ✅ GOOD: O(N + f(C)) — function once
(SELECT auth.uid()) = user_id
Join Optimization
-- ❌ BAD: Subquery per row
user_id IN (SELECT id FROM team_members WHERE team_id = ...)

-- ✅ GOOD: Array comparison
user_id = ANY(ARRAY(SELECT id FROM team_members WHERE team_id = ...))
Null Guards
-- ✅ Always include
auth.uid() IS NOT NULL AND (SELECT auth.uid()) = user_id

Policy Types

  • Use permissive policies by default
  • Use restrictive only for complex multi-condition scenarios
  • Combine policies with OR logic (permissive) or AND logic (restrictive)

Authentication

Client-Side

  • Never trust client-side auth state for sensitive operations
  • Always verify session server-side before mutations
  • Use supabase.auth.getUser() NOT getSession() for security

Server-Side

// ✅ Secure: Validates JWT with Supabase
const { data: { user }, error } = await supabase.auth.getUser();

// ❌ Insecure: Can be spoofed
const { data: { session } } = await supabase.auth.getSession();

Token Handling

  • Never log full tokens
  • Use short-lived access tokens
  • Implement token refresh logic

Edge Functions

Structure

import { serve } from 'https://deno.land/[email protected]/http/server.ts';

serve(async (req) => {
  // CORS handling
  if (req.method === 'OPTIONS') {
    return new Response('ok', { headers: corsHeaders });
  }

  try {
    // Function logic
    return new Response(JSON.stringify({ data }), {
      headers: { ...corsHeaders, 'Content-Type': 'application/json' },
      status: 200,
    });
  } catch (error) {
    return new Response(JSON.stringify({ error: error.message }), {
      headers: { ...corsHeaders, 'Content-Type': 'application/json' },
      status: 400,
    });
  }
});

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

Subscribe to this mod's changes

65-stack-supabase is a cursor rule published in the GitHub repository zoxknez/ai-coding-rules (27 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 934 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.