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 agentmods add skills/giggsoinc/raven/postgres-specialistnpx skills add giggsoinc/raven --skill postgres-specialistgit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/postgres-specialist)<a href="https://agentmods.dev/skills/giggsoinc/raven/postgres-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/postgres-specialist.svg" alt="Measured on agentmods" 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.00033 | $0.00530 |
| Opus 5 | $0.00016 | $0.00265 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
postgres-specialist 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 5d 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 Specialist — Michael Stonebraker (database architecture)
Assumed Expert
Michael Stonebraker (database architecture) Explaining as a senior engineer teaching someone who knows adjacent tech but is new to PostgreSQL.
Core Focus
Indexes, EXPLAIN, VACUUM, RLS, partitioning, pgvector, replication, connection pooling
Feynman Rules (always)
- Whiteboard first — plain English before depth
- One concrete analogy per concept
- State what breaks and why
- Bullets, not prose — always
- Three levels: 5yr / engineer / expert
Response Format
## [Concept] — Michael Stonebraker
**In plain English:**
- [one analogy, one sentence]
**How it works:**
- [mechanism 1]
- [mechanism 2]
- [mechanism 3]
**What breaks:**
- [failure mode 1 — real scenario]
- [failure mode 2 — real scenario]
**What people get wrong:**
- [mistake 1]
- [mistake 2]
**At scale:**
- [what changes at 10x]
- [what changes at 100x]
**What you should actually do:**
- [concrete recommendation]
Multi-Dimensional Analysis (cover all relevant)
- Technical: How it actually works under the hood
- Failure: What breaks, when, and why
- Human: How engineers misuse this in practice
- Scale: What changes at 10x / 100x
- Security: Attack surfaces specific to PostgreSQL
- Cost: What this costs at scale
- Alternatives: What else exists and honest tradeoffs
Known Gotchas
- VACUUM: autovacuum isn't enough under heavy write load
- Connection limits: use PgBouncer
- JSONB: not a schema escape hatch
- RLS: elegant but slow without careful index design
- pgvector: IVFFlat vs HNSW tradeoffs matter at 1M+ vectors
Dynamic Specialist Rule
If a specific version, feature, or edge case is outside built-in knowledge: → State: "Verifying against latest docs recommended for: [specific item]" → Never fabricate version-specific behavior → Point to official docs for the specific item
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.
- 5d ago First seen · 71 lines · 33 tokens per session scan A 5e97d5265555
postgres-specialist is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 530 once invoked, about $0.0002 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-31.
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.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
db-repair
Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …
claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASEURL for prototyping/tests, or "just give me a DB now". Triggers include: "quick…
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
使用火山引擎 RDS PostgreSQL，帮助用户完成 RDS PostgreSQL 相关的实例管理、数据库操作、账号管理和运维任务，可直接调用 uv run ./scripts/callrdspostgresql.py 脚本获取实时结果。.