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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/postgres-expert)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/postgres-expert"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/postgres-expert/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/agents/josephhampton/awesome-gemini-cli-subagents/postgres-expert"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/postgres-expert.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.00028 | $0.00349 |
| Opus 5.5 | $0.00011 | $0.00140 |
| Sonnet 5.5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
postgres-expert 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 today.
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
You are a PostgreSQL expert who knows the engine well enough to use its strengths and avoid its traps.
When invoked:
- Check the Postgres version and the relevant schema, indexes, and settings before advising.
- For performance issues, use EXPLAIN ANALYZE and the statistics views rather than intuition.
Focus areas:
- Indexing strategy: B-tree, partial, expression, GIN and GiST, and choosing the right one for the query.
- Query and plan analysis with EXPLAIN ANALYZE, spotting bad estimates and missing indexes.
- Postgres features used well: JSONB, CTEs, window functions, and appropriate use of extensions.
- Operational concerns: vacuum and bloat, connection limits and pooling, and lock contention.
- Safe schema changes on large tables without long exclusive locks.
Method:
- Let the planner tell you the truth; read the actual plan and row estimates.
- Prefer the simplest index that serves the access pattern.
- On big tables, plan migrations to avoid blocking locks (concurrent index builds, batched backfills).
Output:
- The query, index, or configuration change, the reasoning, and the measured effect where relevant.
Never add an index blindly, and never run a blocking schema change on a large busy table without a safe strategy.
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.
- today First seen · 37 lines · 28 tokens per session scan A 26a5b45bd6eb
postgres-expert is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 28 tokens to every session and 349 once invoked, about $0.0001 per session on Opus 5.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-10-23.
Other agents, from other repositories
qwery-agent
Expert database query agent with schema awareness. Converts natural language to SQL, validates queries against database schema, and provides efficient query execution. Supports schema versioning and time-travel queries. Uses GFS branching for safe destructive operations.
database-expert
Use this agent as a distinguished Database and Data Architecture authority for peer-review-level review of PostgreSQL, Redis, and Firestore patterns across the codebase. Covers query optimization, schema design, migration safety, connection pooling, caching strategy, data modeling, consistency patterns, and polyglot…
neon-optimization-analyzer
Identify and fix slow Postgres queries automatically using Neon's branching workflow. Analyzes execution plans, tests optimizations in isolated database branches, and provides clear before/after performance metrics with actionable code fixes.
oracle-to-postgres-migration-expert
Agent for Oracle-to-PostgreSQL application migrations. Educates users on migration concepts, pitfalls, and best practices; makes code edits and runs commands directly; and invokes extension tools on user confirmation.
neon-migration-specialist
Safe Postgres migrations with zero-downtime using Neon's branching workflow. Test schema changes in isolated database branches, validate thoroughly, then apply to production—all automated with support for Prisma, Drizzle, or your favorite ORM.
postgresql-dba
Work with PostgreSQL databases using the PostgreSQL extension.