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/beel-collab/presets.devWrote 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/beel-collab/presets.dev/supabase-rules)<a href="https://agentmods.dev/rules/beel-collab/presets.dev/supabase-rules"><img src="https://agentmods.dev/badge/rules/beel-collab/presets.dev/supabase-rules/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/beel-collab/presets.dev/supabase-rules"><img src="https://agentmods.dev/badge/rules/beel-collab/presets.dev/supabase-rules.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.00000 | $0.01387 |
| Opus 5.5 | $0.00000 | $0.00555 |
| Sonnet 5.5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
supabase-rules 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase Rules for Cursor: Auth, RLS and Typed Queries
Install
Install the native export at .cursor/rules/supabase-rules.mdc.
Copy that export, not this catalog file. Catalog fields such as tools and author are for presets.dev.
Install one skill file per name. Cursor, GitHub Copilot, Codex, Antigravity CLI, and Devin can all read .agents/skills, so a second copy with the same name collides.
Supabase Rules for Cursor: Auth, RLS and Typed Queries
File-scoped Cursor rule for Supabase. It attaches when a matching file is in context.
Updated for supabase-js 2.119.0, Nov 2026
Do not upgrade dependencies or the framework version unless the task asks.
Project shape
The browser uses a publishable key (sb_publishable_...). A secret key (sb_secret_...) stays on a server you control. Supabase is deprecating the legacy anon and service_role JWT keys by the end of 2026. They still work until you disable them, and a publishable key has the same low privilege as anon. A secret key, like service_role, bypasses RLS. Do not ship either elevated key to a browser. A Next.js or other SSR app creates the server client the way the repo already does, with the request cookies. Do not invent a second auth helper.
SQL lives in migrations. Generated database types are generated. Do not hand-edit the generated file.
Queries and RLS
Every table that holds user data has row level security enabled. Write one policy per command. INSERT checks the new row with WITH CHECK and cannot take USING. DELETE filters existing rows with USING and cannot take WITH CHECK. UPDATE needs both: USING picks the rows that can change, and WITH CHECK accepts the new values. If an UPDATE policy omits WITH CHECK, Postgres reuses USING for the new row. That is valid. Do not flag it as missing. A DELETE policy that only has USING ((select auth.uid()) = user_id) is also valid. A policy of true for every role is a bug unless the table is genuinely public.
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.
- today First seen · 113 lines · 0 tokens per session scan A a1af52016772
supabase-rules is a cursor rule published in the GitHub repository beel-collab/presets.dev (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,387 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-11-13.
supabase-rules compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| supabase-rulesbeel-collab/presets.dev | Cursor rule | 3 | yesterday | MIT | A | 0 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 190k | 15d ago | MIT | A | 604 | Cursor |
| angular-20angular/angular | Cursor rule | 101k | today | MIT | A | 0 | Cursor |
| dev-standardapache/superset | Cursor rule | 76k | today | Apache-2.0 | A | 1,147 | Cursor |
| prefer-direct-imports-over-module-mocksprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |
| config-validation-and-normalizationprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |
| control-plane-descriptorsprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |