postgres-patterns

postgres-patterns is a skill for Kiro from Fmarzochi/EGC. It costs 38 tokens per session (1,054 once invoked), scanned A, a copy of postgres-patterns, Apache-2.0.

A quick reference for designing and improving PostgreSQL databases, including indexes, data types, query patterns, security, and connection pooling.

In plain words
What is it for?
Use it when writing SQL or migrations, designing schemas, troubleshooting query speed, adding indexes, setting up row-level security, or configuring connection pools.
Why use it?
It helps prevent slow queries, unsuitable column types, weak database security, and inefficient schema or connection choices.

Skill for Kiro

Written for Kiro: installed under .kiro/.

Good fit Use it when writing SQL or migrations, designing schemas, troubleshooting query speed, adding indexes, setting up row-level security, or configuring connection pools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fmarzochi/egc/postgres-patterns
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 Fmarzochi/EGC --skill postgres-patterns
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

Made for: Kiro.

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-patterns

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fmarzochi/egc/postgres-patterns"><img src="https://agentmods.dev/badge/skills/fmarzochi/egc/postgres-patterns.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 1,054 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 83% 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.01054
Opus 5.5 $0.00015 $0.00422
Sonnet 5.5 $0.00008 $0.00211
Haiku 4.5 $0.00004 $0.00105

Measured 1mo ago against content hash f99c854ad6ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

postgres-patterns 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.

Origin

This is a copy

83% identical to postgres-patterns — 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.

.kiro/skills/postgres-patterns/SKILL.md · 158 lines

How it starts

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

PostgreSQL Patterns

Quick reference for PostgreSQL best practices. For detailed guidance, use the database-reviewer agent.

When to Activate

  • Writing SQL queries or migrations
  • Designing database schemas
  • Troubleshooting slow queries
  • Implementing Row Level Security
  • Setting up connection pooling

Quick Reference

Index Cheat Sheet

Query Pattern Index Type Example
WHERE col = value B-tree (default) CREATE INDEX idx ON t (col)
WHERE col > value B-tree CREATE INDEX idx ON t (col)
WHERE a = x AND b > y Composite CREATE INDEX idx ON t (a, b)
WHERE jsonb @> '{}' GIN CREATE INDEX idx ON t USING gin (col)
WHERE tsv @@ query GIN CREATE INDEX idx ON t USING gin (col)
Time-series ranges BRIN CREATE INDEX idx ON t USING brin (col)

Data Type Quick Reference

Use Case Correct Type Avoid
IDs bigint int, random UUID
Strings text varchar(255)
Timestamps timestamptz timestamp
Money numeric(10,2) float
Flags boolean varchar, int

Common Patterns

Composite Index Order:

-- Equality columns first, then range columns
CREATE INDEX idx ON orders (status, created_at);
-- Works for: WHERE status = 'pending' AND created_at > '2024-01-01'

Covering Index:

CREATE INDEX idx ON users (email) INCLUDE (name, created_at);
-- Avoids table lookup for SELECT email, name, created_at

Partial Index:

CREATE INDEX idx ON users (email) WHERE deleted_at IS NULL;
-- Smaller index, only includes active users

RLS Policy (Optimized):

CREATE POLICY policy ON orders
  USING ((SELECT auth.uid()) = user_id);  -- Wrap in SELECT!

UPSERT:

INSERT INTO settings (user_id, key, value)
VALUES (123, 'theme', 'dark')
ON CONFLICT (user_id, key)
DO UPDATE SET value = EXCLUDED.value;

Cursor Pagination:

SELECT * FROM products WHERE id > $last_id ORDER BY id LIMIT 20;
-- O(1) vs OFFSET which is O(n)

Read the full file on GitHub · 158 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. 1mo ago First seen · 158 lines · 38 tokens per session scan A f99c854ad6ca

Subscribe to this mod's changes

postgres-patterns is a skill published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,054 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 postgres-patterns, differing in 8 lines, and is treated as a copy.