postgres-best-practices

postgres-best-practices is a skill for Claude Code, Codex from bcastelino/agent-skills-kit. It costs 38 tokens per session (410 once invoked), scanned A, a copy of supabase-postgres-best-practices, MIT.

A guide to designing and tuning PostgreSQL databases, including SQL queries, tables, indexes, connections, security rules, and monitoring. PostgreSQL is a database system used to store and retrieve application data.

In plain words
What is it for?
Use it when writing or reviewing PostgreSQL queries, designing schemas, adding indexes, configuring connections, or working with row-level security.
Why use it?
It helps find common causes of slow queries, unsafe data access, poor database structure, and connection or scaling problems.

Skill for Claude CodeCodex

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

Good fit Use it when writing or reviewing PostgreSQL queries, designing schemas, adding indexes, configuring connections, or working with row-level security.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bcastelino/agent-skills-kit/postgres-best-practices
Install

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.

Any agent
npx skills add bcastelino/agent-skills-kit --skill postgres-best-practices
Clone the repo
git clone --depth 1 https://github.com/bcastelino/agent-skills-kit

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin postgres-best-practices/plugin install postgres-best-practices after adding the marketplace above.

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 postgres-best-practices

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/bcastelino/agent-skills-kit/postgres-best-practices"><img src="https://agentmods.dev/badge/skills/bcastelino/agent-skills-kit/postgres-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 410 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 97% 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.00038 $0.00410
Opus 5 $0.00019 $0.00205
Sonnet 5 $0.00008 $0.00082
Haiku 4.5 $0.00004 $0.00041

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

Security

Grade A, and why

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 8d 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

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

skills/postgres-best-practices/SKILL.md · 54 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. 8d ago First seen · 54 lines · 38 tokens per session scan A c1a6a1da3092

Subscribe to this mod's changes

postgres-best-practices is a skill published in the GitHub repository bcastelino/agent-skills-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 410 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to supabase-postgres-best-practices, differing in 8 lines, and is treated as a copy.