pg-aiguide is a knowledge and tooling project that gives AI coding assistants version-aware PostgreSQL documentation and curated database practices. Developers use it through agent skills, an MCP server, or a Claude Code plugin to help coding tools generate better PostgreSQL code. The catalogue entries are its skills, instructions, MCP integration, and rule.
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.
git clone --depth 1 https://github.com/timescale/pg-aiguideWrote 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/rules/timescale/pg-aiguide/postgres-best-practices)<a href="https://agentmods.dev/rules/timescale/pg-aiguide/postgres-best-practices"><img src="https://agentmods.dev/badge/rules/timescale/pg-aiguide/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/rules/timescale/pg-aiguide/postgres-best-practices"><img src="https://agentmods.dev/badge/rules/timescale/pg-aiguide/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.00000 | $0.00308 |
| Opus 5.5 | $0.00000 | $0.00123 |
| Sonnet 5.5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 10d 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.
What it actually says
PostgreSQL best practices
When writing or reviewing SQL, designing schemas, or working with PostgreSQL:
- Use the
search_docstool to look up PostgreSQL syntax, functions, and behavior for the version in use. - Use
search_docswith sourcetigerwhen working with TimescaleDB or Tiger Cloud features. - Before designing tables, invoke the
design-postgres-tablesskill for data type, constraint, and indexing guidance. - For time-series, IoT, or event data on TimescaleDB, invoke the
setup-timescaledb-hypertablesskill. - For percentiles, rates, time-weighted averages, uptime, or state durations on TimescaleDB, invoke the
timescaledb-hyperfunctionsskill. - When adding vector search with pgvector, invoke the
pgvector-semantic-searchskill. - When combining keyword and semantic search, invoke the
postgres-hybrid-text-searchskill. - Prefer
search_type: "semantic"for natural-language questions andsearch_type: "keyword"for exact term lookups. - Always specify the correct PostgreSQL
versionparameter (14-18 or "latest") to get version-accurate results.
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.
- 10d ago Changed · +1 lines d2eb44c50109
- 1mo ago First seen · 22 lines · 0 tokens per session scan A 3e47969165e0
postgres-best-practices is a cursor rule published in the GitHub repository timescale/pg-aiguide (1,871 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 308 tokens. 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.
Other cursor rules, from other repositories
db
Connect to any database — Cloud SQL, PostgreSQL, Snowflake, Databricks, Athena, Presto, or Oracle.
30-database-postgres
PostgreSQL and persistence rules.
postgresql
PostgreSQL: advanced SQL, performance, extensions.
database-migrations
Role: Database Migration Safety Reviewer. Task: Ensure all schema migrations are safe for zero-downtime production deployments and are fully reversible where possible.
postgresql
PostgreSQL: advanced SQL, performance, extensions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.