SRA: Skill for Claude Code

.agent/skills/supabase-postgres-best-practices/SKILL.md

supabase-postgres-best-practices is a skill for Claude Code, Codex from Aniket-a14/SRA. It costs 41 tokens per session (434 once invoked), scanned A, a copy of supabase-postgres-best-practices, Apache-2.0.

Postgres database guidance from Supabase for writing queries, designing schemas, and configuring databases for reliable performance and access control.

In plain words
What is it for?
It helps optimize SQL, indexes, connection pooling, Row-Level Security rules that limit which rows users can access, schemas, concurrency, monitoring, and data-access patterns.
Why use it?
It helps identify slow queries, missing indexes, connection problems, unsafe data access, and design issues before they affect the application.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

This is Aniket-a14/SRA's own configuration. It tells Claude Code and Codex how to work on SRA itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SRA configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Aniket-a14/SRA. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Aniket-a14/SRA/main/.agent/skills/supabase-postgres-best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Aniket-a14/SRA

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for supabase-postgres-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/aniket-a14/sra/supabase-postgres-best-practices/github.svg)](https://agentmods.dev/skills/aniket-a14/sra/supabase-postgres-best-practices)
Your own site
<a href="https://agentmods.dev/skills/aniket-a14/sra/supabase-postgres-best-practices"><img src="https://agentmods.dev/badge/skills/aniket-a14/sra/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.

agentmods 80×15 button for supabase-postgres-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/aniket-a14/sra/supabase-postgres-best-practices"><img src="https://agentmods.dev/badge/skills/aniket-a14/sra/supabase-postgres-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00434
Opus 5 $0.00020 $0.00217
Sonnet 5 $0.00008 $0.00087
Haiku 4.5 $0.00004 $0.00043

Measured 9d ago against content hash 7ecae0a1ba93, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

Origin

This is a copy

100% identical to supabase-postgres-best-practices — 0 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.

.agent/skills/supabase-postgres-best-practices/SKILL.md · 58 lines

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:

rules/query-missing-indexes.md
rules/schema-partial-indexes.md
rules/_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)

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Changes

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.

  1. 9d ago First seen · 58 lines · 41 tokens per session scan A 7ecae0a1ba93

Subscribe to this mod's changes

supabase-postgres-best-practices is a skill published in the GitHub repository Aniket-a14/SRA (23 stars, last pushed 10d ago), licensed Apache-2.0. It adds 41 tokens to every session and 434 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to supabase-postgres-best-practices, differing in 0 lines, and is treated as a copy.