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 isdaniel/pgtuner_mcp --skill pg-lock-diagnosisgit clone --depth 1 https://github.com/isdaniel/pgtuner_mcpWrote 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/isdaniel/pgtuner_mcp/pg-lock-diagnosis)<a href="https://agentmods.dev/skills/isdaniel/pgtuner_mcp/pg-lock-diagnosis"><img src="https://agentmods.dev/badge/skills/isdaniel/pgtuner_mcp/pg-lock-diagnosis/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/isdaniel/pgtuner_mcp/pg-lock-diagnosis"><img src="https://agentmods.dev/badge/skills/isdaniel/pgtuner_mcp/pg-lock-diagnosis.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.00050 | $0.02773 |
| Opus 5 | $0.00025 | $0.01386 |
| Sonnet 5 | $0.00010 | $0.00555 |
| Haiku 4.5 | $0.00005 | $0.00277 |
Grade A, and why
pg-lock-diagnosis 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 10d 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL Lock Contention Diagnosis
This skill guides investigation and resolution of lock contention issues in PostgreSQL using pgtuner-mcp tools.
When to Use This Skill
Use this skill when the user:
- Reports queries being blocked or timing out
- Sees "Lock" wait events in
pg_stat_activity - Experiences deadlocks (logged in PostgreSQL error log)
- Reports
idle in transactionsessions causing problems - Asks "why are my queries waiting?" or "what is blocking this query?"
- Sees application-level timeout errors due to lock waits
- Reports slow response times during peak concurrent usage
MCP Resources Available
pgtuner://health/locks-- Quick lock health check (lightweight, targeted)pgtuner://health/connections-- Connection state overviewpgtuner://settings/connections-- Connection and timeout configuration
Related MCP Prompt
This skill extends the lock analysis portions of the health_check MCP Prompt (which checks locks at a surface level).
Prerequisites
- The pgtuner-mcp server must be connected with a valid
DATABASE_URI - Access to
pg_stat_activity,pg_lockssystem views
Agent Decision Tree
What is the user's symptom?
|
+--> "Queries are being blocked / timing out"
| --> Start with Step 1 (Active Queries) to find blockers
|
+--> "Deadlock errors in logs"
| --> Start with Step 2 (Wait Events) then Step 1 with include_idle
|
+--> "idle in transaction problems"
| --> Start with Step 1 (include_idle: true, min_duration_seconds: 60)
|
+--> "General lock performance concerns"
| --> Start with Step 3 (Health Check for locks) then Step 2
|
+--> "Lock waits during maintenance (VACUUM, REINDEX, etc.)"
--> Start with Step 1 then check Step 4 (Configuration)
Lock Investigation Workflow
Step 1: Identify Active Queries and Blockers
Tool: get_active_queries
Parameters:
include_idle: true
include_system: false
min_duration_seconds: 0
What to look for:
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.
- 10d ago First seen · 323 lines · 50 tokens per session scan A 6bf87f0a4c36
pg-lock-diagnosis is a skill published in the GitHub repository isdaniel/pgtuner_mcp (29 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,773 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
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
exasol-table-design
Exasol table design for performance: DISTRIBUTE BY, PARTITION BY, zone maps, data types, replication, surrogate keys, and CREATE TABLE syntax.
exasol-udfs
Exasol User-Defined Functions (UDFs) and Scripts: CREATE SCRIPT syntax, language options, SQL-to-language data type mappings, ExaIterator API, BucketFS access, and Script Language Containers.
exasol-import-export
Exasol IMPORT and EXPORT SQL statements: syntax, file formats (CSV, FBV, Parquet), cloud storage (S3, Azure, GCS), connection objects, error handling, and ETL staging patterns.
exasol-system-tables
Exasol system and statistics tables: what they contain, visibility prefixes (EXAALL, EXADBA, EXAUSER), and when to query them directly vs using MCP tools.
exasol-sql-dialect
Exasol SQL dialect specifics: syntax, data types, functions, and common pitfalls for generating correct Exasol SQL.