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/squirrelogic/cursor-rules/supabase-drizzle-bootstrapgit clone --depth 1 https://github.com/squirrelogic/cursor-rulesWhat 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 | $0.00000 | $0.01704 |
| Opus 5 | $0.00000 | $0.00852 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade A, and why
supabase-drizzle-bootstrap 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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap Drizzle with Supabase
Overview
Guidelines for setting up and using Drizzle ORM with Supabase PostgreSQL.
actions:
-
type: suggest message: | When setting up Drizzle with Supabase:
- Install required dependencies:
npm install drizzle-orm pg @types/pg postgres jwt-decode npm install -D drizzle-kit- Create a drizzle config file (drizzle.config.ts):
import { config } from 'dotenv'; import { defineConfig } from 'drizzle-kit'; config({ path: '.env' }); export default defineConfig({ schema: './db/schema/index.ts', out: './supabase/migrations', dialect: 'postgresql', dbCredentials: { url: process.env.DATABASE_URL!, }, });- Schema files should be organized as:
src/ └── db/ ├── schema/ │ ├── index.ts // exports all schema definitions. │ ├── auth.ts │ ├── todos.ts │ └── ... ├── drizzle.ts ├── index.ts └── jwt.ts- Example schema structure:
import { eq } from 'drizzle-orm' import { pgTable, text, timestamp, uuid } from 'drizzle-orm/pg-core' import { authUid, authUsers, authenticatedRole } from 'drizzle-orm/supabase' export const todos = pgTable('todos', { id: uuid('id').defaultRandom().primaryKey(), title: text('title').notNull(), completed: boolean('completed').notNull().default(false), created_at: timestamp('created_at').defaultNow().notNull(), user_id: uuid('user_id').notNull().references(() => authUsers.id, { onDelete: "cascade" }) }, (table) => [ // Row Level Security is defined here pgPolicy("users can insert their own todos", { for: "insert", to: authenticatedRole, withCheck: eq(table.id, authUid) }), pgPolicy("users can update their own todos", { for: "update", to: authenticatedRole, using: eq(table.id, authUid), withCheck: eq(table.id, authUid), }), ])
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 · 243 lines · 1,704 tokens per session scan A b52603eb25be
supabase-drizzle-bootstrap is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,704 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.
Other cursor rules, from other repositories
netlify-database-migration-from-extension
Switching to Netlify Database. Reference for the netlify-database skill.
cursorrules
You are an expert in Ruby on Rails, PostgreSQL, Hotwire (Turbo and Stimulus), and Tailwind CSS.
docker-database
Docker configuration for PostgreSQL database and Elasticsearch.
create-rls-policies
Guidelines for writing Postgres migrations.
supabase-migrations
You are a Postgres Expert who loves creating secure database schemas.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.