470-postgresql

A set of rules for designing PostgreSQL databases, including naming, constraints, indexes, security, migrations, backups, and documentation.

In plain words
What is it for?
Use it when creating or reviewing PostgreSQL tables, relationships, indexes, permissions, and version-controlled database migrations.
Why use it?
It helps prevent inconsistent schemas, unsafe database changes, weak access controls, and avoidable query-performance problems.

Cursor rule

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.

agentmods
npx agentmods add rules/d-padmanabhan/agent-engineering-handbook/470-postgresql
Clone the repo
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbook
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00013 $0.05889
Opus 5 $0.00006 $0.02944
Sonnet 5 $0.00003 $0.01178
Haiku 4.5 $0.00001 $0.00589

Measured 2d ago against content hash ccb656bf4fbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

470-postgresql 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.

rules/470-postgresql.mdc · 983 lines

How it starts

The opening of the file, as written. The whole thing — 983 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PostgreSQL Engineering Ruleset

Audience: engineers designing and reviewing PostgreSQL database schemas and migrations Goal: Consistent database schema design with clear naming conventions and maintainable patterns

PostgreSQL Philosophy (Core Principles)

Core Principles:

  • "Consistency is king" - Follow naming conventions consistently across all tables and columns
  • "Explicit over implicit" - Use explicit constraints, types, and defaults
  • "Performance by design" - Index foreign keys and frequently queried columns
  • "Security by default" - Use parameterized queries, RLS, least privilege
  • "Migrations are code" - Version control migrations, make them reversible
  • "Documentation matters" - Comments explain why, not just what
  • "Test your migrations" - Test migrations in staging before production
  • "Backup before changes" - Always backup before destructive operations

Applying PostgreSQL Principles:

-- BAD: Inconsistent naming, no constraints, no indexes
CREATE TABLE User (
    userId SERIAL PRIMARY KEY,
    Email VARCHAR(255),
    firstName VARCHAR(100),
    lastName VARCHAR(100)
);

-- GOOD: Consistent naming, constraints, indexes
CREATE TABLE users (
    id BIGSERIAL PRIMARY KEY,
    email VARCHAR(255) NOT NULL,
    first_name VARCHAR(100) NOT NULL,
    last_name VARCHAR(100) NOT NULL,
    created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
    updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,

    CONSTRAINT users_email_unique UNIQUE (email),
    CONSTRAINT users_email_format CHECK (email ~* '^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}$')
);

CREATE INDEX idx_users_email ON users(email);
CREATE INDEX idx_users_created_at ON users(created_at);

Naming Conventions

Tables

Tables use plural snake_case:

--  GOOD: Plural snake_case
CREATE TABLE users (
    id BIGSERIAL PRIMARY KEY,
    email VARCHAR(255) NOT NULL UNIQUE,
    created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
);

CREATE TABLE user_books (
    id BIGSERIAL PRIMARY KEY,
    user_id BIGINT NOT NULL REFERENCES users(id),
    book_id BIGINT NOT NULL REFERENCES books(id),
    created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),
    UNIQUE(user_id, book_id)
);

--  BAD: Singular or camelCase
CREATE TABLE User ( ... );
CREATE TABLE userBooks ( ... );

Read the full file on GitHub · 983 lines

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. 2d ago First seen · 983 lines · 13 tokens per session scan A ccb656bf4fbf

Subscribe to this mod's changes

470-postgresql is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (15 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 5,889 once invoked, about $0.0001 per session on Opus 5. 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.