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 postgres-concurrent-schema-init-deadlockgit 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/postgres-concurrent-schema-init-deadlock)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/postgres-concurrent-schema-init-deadlock"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/postgres-concurrent-schema-init-deadlock/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/postgres-concurrent-schema-init-deadlock"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/postgres-concurrent-schema-init-deadlock.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.00124 | $0.00984 |
| Opus 5.5 | $0.00050 | $0.00394 |
| Sonnet 5.5 | $0.00025 | $0.00197 |
| Haiku 4.5 | $0.00012 | $0.00098 |
Grade A, and why
postgres-concurrent-schema-init-deadlock 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.
PostgreSQL Concurrent Schema Init Deadlock
Problem
Multiple worker processes (Cloud Run jobs, K8s pods, serverless functions) starting simultaneously all try to run schema initialization code, causing PostgreSQL deadlocks even when using "IF NOT EXISTS" clauses.
Context / Trigger Conditions
- Error:
psycopg2.errors.DeadlockDetected: deadlock detected - Log shows:
Process X waits for RowExclusiveLock on relation... blocked by process Y - Multiple workers/jobs starting at roughly the same time
- Each worker calls
init_schema()or runs migrations at startup - Using
CREATE TABLE IF NOT EXISTSorCREATE INDEX IF NOT EXISTS
Why This Happens
PostgreSQL's IF NOT EXISTS is not concurrent-safe:
CREATE INDEX IF NOT EXISTSstill acquires locks before checking existence- Multiple processes acquiring locks on different objects can deadlock
- Even "safe" DDL can conflict when executed concurrently
Solution
Option 1: Skip Init in Production (Recommended)
Schema already exists - don't run init_schema() in workers:
with Database() as db:
# Schema already exists in production - skip to avoid deadlocks
# db.init_schema()
# ... worker code
Option 2: Use Advisory Locks
Serialize schema init with PostgreSQL advisory locks:
def init_schema_safe(self):
cursor = self._cursor()
# Acquire advisory lock (blocks other processes)
cursor.execute("SELECT pg_advisory_lock(12345)")
try:
self.init_schema()
finally:
cursor.execute("SELECT pg_advisory_unlock(12345)")
self.conn.commit()
Option 3: Separate Migration Step
Run migrations as a separate job before starting workers:
# In deployment pipeline
python -m src.migrate # Single process, runs first
# Then start workers
gcloud run jobs execute worker-job
Option 4: Lock Timeout + Retry
Set lock timeout and retry on deadlock:
def init_schema_with_retry(self, max_retries=3):
for attempt in range(max_retries):
try:
cursor = self._cursor()
cursor.execute("SET lock_timeout = '5s'")
self.init_schema()
return
except psycopg2.errors.DeadlockDetected:
self.conn.rollback()
if attempt == max_retries - 1:
raise
time.sleep(random.uniform(1, 3))
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 · 124 tokens per session scan A 74aa616750f5
postgres-concurrent-schema-init-deadlock is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 124 tokens to every session and 984 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-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.
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…