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/vibestackdev/vibe-stackWrote 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/vibestackdev/vibe-stack/supabase-rls)<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/supabase-rls"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/supabase-rls/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/vibestackdev/vibe-stack/supabase-rls"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/supabase-rls.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.00188 |
| Opus 5.5 | $0.00000 | $0.00075 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
supabase-rls 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.
What it actually says
Supabase Row Level Security (RLS)
ALWAYS assume RLS is enabled. NEVER generate queries that assume admin access by default.
RLS Policy Patterns: -- Own record only:
create policy "Users own data" on todos
for all using (auth.uid() = user_id);
-- Read-only public:
create policy "Public read" on posts
for select using (published = true);
Code rules:
- ALWAYS use anon/authenticated clients (not
service_role) for user operations - Service role client: ONLY use in server-to-server operations (webhooks, cron jobs)
- NEVER pass
service_rolekey to the browser - Use
select('specific, columns')notselect('*')for performance
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.
- 1mo ago First seen · 28 lines · 0 tokens per session scan A ed44abc31c3c
supabase-rls is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 188 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-31.
Other cursor rules, from other repositories
database-patterns
Use the createTable function with consistent naming.
local-storage-patterns
Shipkit uses browser local storage as a fallback when no database is configured. This provides a zero-config development experience while maintaining feature parity with database mode.
payload-configuration
Shipkit conditionally initializes Payload CMS based on environment variables. The src/payload.config.ts file handles graceful degradation when no database is configured.
supabase-db-rls
Guidelines for writing Postgres Row Level Security policies.
graceful-degradation
Shipkit implements graceful degradation to provide a seamless experience whether users have a database configured or not. When no DATABASEURL is provided, the application automatically falls back to local storage for data persistence.
waitlist-implementation
Shipkit includes a complete waitlist feature for product launches. The implementation follows Next.js App Router patterns with Server Components, Server Actions, and Drizzle ORM.