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.
npx agentmods add rules/kensaurus/cursor-kenji/supabasegit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/supabase)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/supabase"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/supabase.svg" alt="Measured on agentmods" 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.00310 |
| Opus 5 | $0.00000 | $0.00155 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
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.
What it actually says
Supabase Conventions
Client Usage
- Use typed Supabase client from
@/lib/supabase - Always use
.select()with specific columns (neverSELECT *) - Use
.single()when expecting one row - Handle errors:
const { data, error } = await supabase.from(...)
RLS
- Every table MUST have RLS enabled
- Test policies after creation with Supabase MCP
- Use
auth.uid()for user-scoped access - Use
EXISTSsubqueries for role-based access (avoid function calls in policies)
Migrations
- File naming:
YYYYMMDD_description.sql - Always include
created_at TIMESTAMPTZ DEFAULT now() - Always include
updated_atwith moddatetime trigger - Always add indexes on foreign keys
- After migration: regenerate types with
supabase gen types typescript
Edge Functions
- Verify JWT or API key in every function
- Handle CORS preflight OPTIONS requests
- Return proper status codes (401, 403, 400, 500)
- Use
Deno.env.get()for secrets
Data Fetching
- Server Components: use Supabase server client directly
- Client Components: use TanStack Query with Supabase client
- Real-time: subscribe at component level, cleanup on unmount
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.
- 2d ago First seen · 38 lines · 0 tokens per session scan A 140240a0dfc5
supabase is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 310 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-09-03.
Other cursor rules, from other repositories
query-patterns
Database query patterns, optimization, and safety rules. Apply when writing or editing queries.
schema-design
Database schema design conventions and standards. Apply when designing schema or migrations.
migration-rules
Database migration patterns and safety rules. Apply when creating or editing migrations.
integration-testing
Integration testing patterns and database test setup.
sql
Rules for SQL files (queries, migrations, stored procs).
mysql-auto
This rule enforces MySQL-specific best practices to enhance readability, performance, security, and maintainability. It targets MySQL features (e.g., storage engines, character sets) and common pitfalls, and adds concrete guidance for schema design and creation.