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/divinevideo/divine-mobile/pg-pool-cloudsql-reconnectnpx skills add divinevideo/divine-mobile --skill pg-pool-cloudsql-reconnectgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/pg-pool-cloudsql-reconnect)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/pg-pool-cloudsql-reconnect"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/pg-pool-cloudsql-reconnect.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.00117 | $0.01113 |
| Opus 5 | $0.00059 | $0.00557 |
| Sonnet 5 | $0.00023 | $0.00223 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
pg-pool-cloudsql-reconnect 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 yesterday.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pg-pool CloudSQL Reconnection
Problem
Node.js applications using pg-pool with CloudSQL (or other managed PostgreSQL) fail to
recover from connection resets. Retry logic appears to work but keeps failing with the
same ECONNRESET error because the pool caches dead connections.
Context / Trigger Conditions
- ECONNRESET errors that persist despite retry logic
- Error messages like:
read ECONNRESETConnection terminatedconnection already closedremaining connection slots are reserved for non-replication superuser connections
- High-concurrency applications (parallel batch processing)
- CloudSQL with small instance tiers (db-f1-micro, db-g1-small)
- Long-running scripts with periods of inactivity followed by bursts
Root Cause
pg-pool maintains a pool of database connections. When CloudSQL resets connections (due to timeout, maintenance, or connection limits), the pool still holds references to those dead connections. Simply retrying the operation uses the same dead connection from the pool.
Solution
Instead of just retrying, recreate the entire pool on connection reset errors:
export class PostgresDatabase {
private pool: Pool;
private config: PostgresConfig;
constructor(config: PostgresConfig) {
this.config = config;
this.pool = this.createPool();
}
private createPool(): Pool {
const pool = new Pool({
...this.config,
max: 25, // Adequate for concurrency
idleTimeoutMillis: 30000, // Close idle connections
connectionTimeoutMillis: 10000, // Timeout for new connections
keepAlive: true, // TCP keepalive
});
pool.on('error', (err) => {
console.error('Pool error:', err.message);
});
return pool;
}
private async reconnect(): Promise<void> {
console.log("Reconnecting to database...");
try {
await this.pool.end();
} catch {
// Ignore cleanup errors
}
this.pool = this.createPool();
await this.pool.query("SELECT 1"); // Verify connection
console.log("Database reconnected");
}
private async withRetry<T>(
operation: () => Promise<T>,
maxRetries = 3
): Promise<T> {
for (let attempt = 0; attempt < maxRetries; attempt++) {
try {
return await operation();
} catch (error) {
const msg = error instanceof Error ? error.message : String(error);
const needsReconnect =
msg.includes("ECONNRESET") ||
msg.includes("Connection terminated") ||
msg.includes("connection already closed") ||
msg.includes("remaining connection slots");
if (!needsReconnect || attempt === maxRetries - 1) {
throw error;
}
const delay = 1000 * Math.pow(2, attempt);
console.log(`Connection error, reconnecting in ${delay}ms...`);
await new Promise(r => setTimeout(r, delay));
// KEY: Recreate the pool, don't just retry
await this.reconnect();
}
}
throw new Error("Max retries exceeded");
}
}
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.
- yesterday First seen · 150 lines · 117 tokens per session scan A 20e0865d843b
pg-pool-cloudsql-reconnect is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 117 tokens to every session and 1,113 once invoked, about $0.0006 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-09-03.
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.
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…
analyzing-insights-across-teams
Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard…
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…
nw-database-technology-selection
Database comparison catalogs, RDBMS vs NoSQL selection criteria, CAP/ACID/BASE theory, OLTP vs OLAP, and technology-specific characteristics.