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 agents/domengabrovsek/claude/postgresql-expertgit clone --depth 1 https://github.com/domengabrovsek/claudeWrote 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/domengabrovsek/claude/postgresql-expert)<a href="https://agentmods.dev/agents/domengabrovsek/claude/postgresql-expert"><img src="https://agentmods.dev/badge/agents/domengabrovsek/claude/postgresql-expert.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 | $0.00060 | $0.01017 |
| Opus 5 | $0.00030 | $0.00508 |
| Sonnet 5 | $0.00012 | $0.00203 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
PostgreSQL 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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 61 lines · 60 tokens per session scan A f4f9404b5d6b
PostgreSQL Expert is an agent published in the GitHub repository domengabrovsek/claude (15 stars, last pushed 6d ago), with no licence file. It adds 60 tokens to every session and 1,017 once invoked, about $0.0003 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-30.
Other agents, from other repositories
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
database-postgresql
PostgreSQL/Supabase database specialist. Schema design, RLS, query optimization, migrations. Runs on "PostgreSQL", "Supabase", "Postgres query", "RLS" requests.
Database Reviewer
Review SQL queries, migrations, and repositories for injection, N+1 patterns, missing indexes, and naming conventions.
migration-builder
You are a Supabase migration specialist for your project. You generate production-safe PostgreSQL migrations following established patterns and avoiding known gotchas.
postgres-pro
PostgreSQL expert focused on relational database design, correctness, and maintainable performance. Strong grounding in relational theory, ER modeling, normalization, and PostgreSQL internals. Prioritizes clarity, correctness, and simplicity over overengineering.