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/irsyadjpp/postgres-mcp-server/deadlock-transactionnpx skills add irsyadjpp/postgres-mcp-server --skill deadlock-transactiongit clone --depth 1 https://github.com/irsyadjpp/postgres-mcp-serverWrote 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/irsyadjpp/postgres-mcp-server/deadlock-transaction)<a href="https://agentmods.dev/skills/irsyadjpp/postgres-mcp-server/deadlock-transaction"><img src="https://agentmods.dev/badge/skills/irsyadjpp/postgres-mcp-server/deadlock-transaction.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.00039 | $0.00219 |
| Opus 5 | $0.00019 | $0.00110 |
| Sonnet 5 | $0.00008 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
deadlock-transaction 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 4d 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.
What it actually says
Workflow:
- Run deadlock_analysis to check for deadlock risks and lock wait information
- Run transaction_monitor to see active transactions, isolation levels, and long-running transactions
- Run connection_leak to detect connection leaks that may hold locks
- Run connection_pool to check for connection pool exhaustion
- Run get_connections to see all connections and their states
Key recommendations:
- Set appropriate lock_timeout: SET lock_timeout = 5000 (5 seconds)
- Use consistent table access order across transactions
- Keep transactions short and minimize lock hold time
- Use SELECT ... FOR UPDATE SKIP LOCKED to avoid blocking
- Consider READ COMMITTED instead of SERIALIZABLE when possible
- Set @Transactional(timeout) values in Spring Boot
- Use REQUIRES_NEW propagation for independent transactions
- Monitor lock_timeout setting to prevent indefinite waits
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.
- 4d ago First seen · 21 lines · 39 tokens per session scan A c9d9fabc12a3
deadlock-transaction is a skill published in the GitHub repository irsyadjpp/postgres-mcp-server (0 stars, last pushed 29d ago), licensed ISC. It adds 39 tokens to every session and 219 once invoked, about $0.0002 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-31.
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 …
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…
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
使用火山引擎 RDS PostgreSQL，帮助用户完成 RDS PostgreSQL 相关的实例管理、数据库操作、账号管理和运维任务，可直接调用 uv run ./scripts/callrdspostgresql.py 脚本获取实时结果。.