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 divinevideo/divine-mobile --skill cloudsql-idle-connection-timeoutgit 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/cloudsql-idle-connection-timeout)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/cloudsql-idle-connection-timeout"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/cloudsql-idle-connection-timeout/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/divinevideo/divine-mobile/cloudsql-idle-connection-timeout"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/cloudsql-idle-connection-timeout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.01063 |
| Opus 5.5 | $0.00051 | $0.00425 |
| Sonnet 5.5 | $0.00025 | $0.00213 |
| Haiku 4.5 | $0.00013 | $0.00106 |
Grade A, and why
cloudsql-idle-connection-timeout 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 1mo 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud SQL Idle Connection Timeout Fix
Problem
Cloud SQL (and other managed PostgreSQL services) kill idle connections after a timeout (typically 10 minutes). Long-running scripts that open a DB connection early, then perform non-DB work (HTTP requests, file I/O, CDX scanning), then try to use the DB connection again will get a misleading error.
Context / Trigger Conditions
psycopg2.OperationalError: could not receive data from server: Operation timed outpsycopg2.InterfaceError: connection already closed- Script has phases: DB setup → long non-DB work → DB writes
- Using Google Cloud SQL, AWS RDS, or Azure Database for PostgreSQL
- Connection was working initially, fails after idle period
- The error appears AFTER a phase that doesn't use the DB (e.g., API crawling, file processing)
Solution
Pattern 1: Defer DB Connection (Preferred)
Structure code so the DB connection opens AFTER the non-DB phase:
# BAD: Connection opens before long CDX scan
with VineDatabase() as db:
ensure_schema(db)
results = long_running_api_scan() # 5-10 minutes, no DB needed
process_results(db, results) # Connection dead here!
# GOOD: CDX scan first, then fresh DB connection
results = long_running_api_scan() # No DB connection open
with VineDatabase() as db: # Fresh connection when actually needed
ensure_schema(db)
process_results(db, results)
Pattern 2: Reconnection Logic (For Long Batch Operations)
For operations that DO use the DB but might exceed the idle timeout between writes:
import psycopg2
def reconnect_db():
"""Create a fresh database connection."""
db = VineDatabase()
cursor = db._cursor()
return db, cursor
def process_batch(db, cursor, items):
for item in items:
data = fetch_from_api(item) # Slow network call
try:
cursor.execute("INSERT INTO ...", data)
db.conn.commit()
except (psycopg2.OperationalError, psycopg2.InterfaceError):
# Connection died, reconnect and retry
try:
db.close()
except Exception:
pass
db, cursor = reconnect_db()
cursor.execute("INSERT INTO ...", data)
db.conn.commit()
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.
- 1mo ago First seen · 125 lines · 127 tokens per session scan A 30e1b680c4cb
cloudsql-idle-connection-timeout is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 127 tokens to every session and 1,063 once invoked, about $0.0005 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-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 …
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.
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…