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.
npx skills add cookieMonsterDev/agents-skills --skill postgresql-18-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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/skills/cookiemonsterdev/agents-skills/postgresql-18-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/postgresql-18-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/postgresql-18-docs/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/skills/cookiemonsterdev/agents-skills/postgresql-18-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/postgresql-18-docs.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.00081 | $0.01236 |
| Opus 5.5 | $0.00032 | $0.00494 |
| Sonnet 5.5 | $0.00016 | $0.00247 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
postgresql-18-docs 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.
This is a copy
91% identical to postgresql-16-docs — 22 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL questions are easy to answer from stale memory or the wrong major version. Use this skill to ground answers in the official PostgreSQL 18 documentation and return the closest authoritative page instead of generic database advice.
When to Use
Use this skill when the request is about:
- PostgreSQL concepts, terminology, or product boundaries
- SQL syntax, DDL, DML, queries, data types, functions, operators, or type conversion
- Indexes, full text search, concurrency, MVCC, locking, or isolation levels
- Query performance, planner behavior, parallel query, or statistics
- Installation, server setup, configuration parameters, or runtime operation
- Client authentication, roles, privileges, databases, schemas, or localization
- Routine maintenance, vacuuming, backups, restore, or WAL
- High availability, physical replication, logical replication, or failover
- Monitoring, activity views, logs, or troubleshooting server behavior
- Client interfaces such as libpq, large objects, ECPG, or the information schema
- Server programming: triggers, event triggers, rules, PL/pgSQL, SPI, or extensions
- SQL command reference, client utilities, or server applications
- PostgreSQL 18 release notes, new features, or version-specific behavior
Do not use this skill for:
- A different PostgreSQL major version when the user explicitly needs that version. Say which version you are using and offer to switch docs if needed.
- Application framework ORM configuration unless the question is specifically about PostgreSQL behavior or SQL.
- Managed cloud database console operations when the question is about provider-specific UI rather than PostgreSQL docs.
- Non-PostgreSQL databases such as MySQL, SQLite, or MongoDB.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started or tutorials
- SQL language and data modeling
- Query writing and performance
- Server administration and configuration
- Security, roles, and authentication
- Backup, restore, and reliability
- Replication and high availability
- Monitoring and troubleshooting
- Client interfaces and drivers
- Server programming and extensions
- SQL or utility reference
- Internals, limits, or appendix material
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 111 lines · 81 tokens per session scan A 9ed77d1913a0
postgresql-18-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (6 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 1,236 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to postgresql-16-docs, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
cloud-sql-basics
This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source…
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the…
sql-optimizer
Analyzes SQL queries for missing indexes, N+1 patterns, suboptimal joins, and full table scans. Interprets EXPLAIN, detects anti-patterns, rewrites queries. Triggers on: "optimize this query", "slow query", "add indexes", "explain plan", "N+1 query", "why is this query slow".
yida-db-seq-fix
A tool for checking and correcting PostgreSQL sequences, which generate automatic numeric IDs for new rows. It is designed for Yida databases after automatic table creation or data migration.