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 Hainrixz/claude-db --skill db-connection-poolinggit clone --depth 1 https://github.com/Hainrixz/claude-dbWrote 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/hainrixz/claude-db/db-connection-pooling)<a href="https://agentmods.dev/skills/hainrixz/claude-db/db-connection-pooling"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-db/db-connection-pooling/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/hainrixz/claude-db/db-connection-pooling"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-db/db-connection-pooling.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.00055 | $0.01169 |
| Opus 5 | $0.00028 | $0.00584 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
db-connection-pooling 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
db-connection-pooling (M15)
Connection exhaustion is a top cause of production outages and a pure Performance & Scale (axis
performance) concern. Feeds relational Pooling w10 (and the Conexión category in every NoSQL
profile). The dominant modern failure is serverless functions opening one direct connection each and
saturating the backend.
What it checks
- Serverless + direct Postgres — a function/edge runtime (Vercel/Lambda/Cloudflare/Netlify)
connecting directly to Postgres with no pooler. Each cold start opens a connection; concurrency
spikes blow past
max_connections. Recommend a transaction-mode pooler or a serverless driver (Neon/@neondatabase/serverless, Supabase pooler, PlanetScale HTTP). - Transaction-mode pooler misuse — using a transaction-pooling endpoint (PgBouncer
transactionmode, Supabase port 6543) while relying on session features it breaks: server-side prepared statements,SET/session GUCs,LISTEN/NOTIFY, advisory-session locks. - Pool sizing — application pool
max× instance count exceeding backendmax_connections, or a pool so small it serializes requests.
Sizing block
- The server-connection ceiling is roughly a small multiple of vCPU, not your peak concurrency.
Frame
(cores*2) + effective_spindlesas the server-side ceiling on usefully-busy backend connections — not a per-app-pool target. - Size the client pool to that ceiling, not to peak request concurrency. More backend connections than the server can usefully run just adds context-switch and lock contention; queue at the pool, not the database.
- Reserve headroom below
max_connections— leavesuperuser_reserved_connections(and room for other apps/replication) free so an admin can still connect when the pool saturates. - PgBouncer transaction mode multiplexes many client connections onto a few backend connections, so
the client pool can far exceed the backend ceiling — but session-level features break under it
(server-side prepared statements,
SET/session GUCs,LISTEN/NOTIFY, session-scoped advisory locks).
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.
- 9d ago First seen · 86 lines · 55 tokens per session scan A 311e8c318077
db-connection-pooling is a skill published in the GitHub repository Hainrixz/claude-db (19 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 1,169 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 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 …
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
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.