Borrowing it
Nothing to install: this file belongs to kupzed/catatz. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kupzed/catatz/master/.agents/skills/supabase-postgres-best-practices/SKILL.mdgit clone --depth 1 https://github.com/kupzed/catatzWrote 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/skills/kupzed/catatz/supabase-postgres-best-practices)<a href="https://agentmods.dev/skills/kupzed/catatz/supabase-postgres-best-practices"><img src="https://agentmods.dev/badge/skills/kupzed/catatz/supabase-postgres-best-practices/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/skills/kupzed/catatz/supabase-postgres-best-practices"><img src="https://agentmods.dev/badge/skills/kupzed/catatz/supabase-postgres-best-practices.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.00041 | $0.00565 |
| Opus 5.5 | $0.00016 | $0.00226 |
| Sonnet 5.5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
supabase-postgres-best-practices 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.
This is a copy
83% identical to supabase-postgres-best-practices — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Supabase Postgres Best Practices
Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.
When to Apply
Reference these guidelines when:
- Writing SQL queries or designing schemas
- Implementing indexes or query optimization
- Reviewing database performance issues
- Configuring connection pooling or scaling
- Optimizing for Postgres-specific features
- Working with Row-Level Security (RLS)
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Query Performance | CRITICAL | query- |
| 2 | Connection Management | CRITICAL | conn- |
| 3 | Security & RLS | CRITICAL | security- |
| 4 | Schema Design | HIGH | schema- |
| 5 | Concurrency & Locking | MEDIUM-HIGH | lock- |
| 6 | Data Access Patterns | MEDIUM | data- |
| 7 | Monitoring & Diagnostics | LOW-MEDIUM | monitor- |
| 8 | Advanced Features | LOW | advanced- |
How to Use
Read individual rule files for detailed explanations and SQL examples:
references/query-missing-indexes.md
references/query-partial-indexes.md
references/_sections.md
Each rule file contains:
- Brief explanation of why it matters
- Incorrect SQL example with explanation
- Correct SQL example with explanation
- Optional EXPLAIN output or metrics
- Additional context and references
- Supabase-specific notes (when applicable)
References
What ships with it
34 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/_contributing.md 4.0 KB
- references/_sections.md 1.6 KB
- references/_template.md 1.0 KB
- references/advanced-full-text-search.md 1.4 KB
- references/advanced-jsonb-indexing.md 1.4 KB
- references/conn-idle-timeout.md 1.3 KB
- references/conn-limits.md 1.3 KB
- references/conn-pooling.md 1.3 KB
- references/conn-prepared-statements.md 1.5 KB
- references/data-batch-inserts.md 1.3 KB
- references/data-n-plus-one.md 1.3 KB
- references/data-pagination.md 1.3 KB
- references/data-upsert.md 1.4 KB
- references/lock-advisory.md 1.5 KB
- references/lock-deadlock-prevention.md 1.8 KB
- references/lock-short-transactions.md 1.3 KB
- references/lock-skip-locked.md 1.3 KB
- references/monitor-explain-analyze.md 1.4 KB
- references/monitor-pg-stat-statements.md 1.4 KB
- references/monitor-vacuum-analyze.md 1.5 KB
- references/query-composite-indexes.md 1.4 KB
- references/query-covering-indexes.md 1.3 KB
- references/query-index-types.md 1.5 KB
- references/query-missing-indexes.md 1.2 KB
- references/query-partial-indexes.md 1.3 KB
- references/schema-constraints.md 1.8 KB
- references/schema-data-types.md 1.4 KB
- references/schema-foreign-key-indexes.md 1.6 KB
- references/schema-lowercase-identifiers.md 1.7 KB
- references/schema-partitioning.md 1.5 KB
- references/schema-primary-keys.md 1.8 KB
- references/security-privileges.md 1.5 KB
- references/security-rls-basics.md 1.3 KB
- references/security-rls-performance.md 2.1 KB
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 · 65 lines · 41 tokens per session scan A ccd6e4596bd5
supabase-postgres-best-practices is a skill published in the GitHub repository kupzed/catatz (34 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 565 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to supabase-postgres-best-practices, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
querying-production-databases-via-metabase
Runs read-only production database analysis through PostHog's internal Metabase instances. Use for ClickHouse query logs, slow query cost, Postgres query plans, index selection, or tenant-size analysis. Covers US and EU database discovery, SSO login through hogli, safe query rules, and query patterns for both engines.
profiling-slow-api-endpoints
Profiles slow PostHog API endpoints when the main cost is in Postgres or Python. Use when a screen, picker, or list is slow; a Django endpoint has high tail latency; a query plan changes with tenant size; or a proposed database fix needs production evidence. Covers APM traces, safe production EXPLAIN, representative…
system-design-data-architecture
Design system data flows and data-layer ownership, consistency, and store choices from access patterns. Use for critical-flow design, DFD semantic review, data lineage, authority, replication, retention, or a data-tier bottleneck. Avoid unrelated framework stream/dataframe implementation questions.
android-persistence
Implement Room schemas and DataStore preferences with proper async patterns in Android. Use when the primary task is storage schema, DAO, migration, or preference isolation; defer auth-token/security storage, any CoroutineWorker/WorkManager task, Hilt graph wiring, and cache-policy design.