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-io-deep-divegit 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-io-deep-dive)<a href="https://agentmods.dev/skills/isdaniel/pgtuner_mcp/pg-io-deep-dive"><img src="https://agentmods.dev/badge/skills/isdaniel/pgtuner_mcp/pg-io-deep-dive/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-io-deep-dive"><img src="https://agentmods.dev/badge/skills/isdaniel/pgtuner_mcp/pg-io-deep-dive.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.00067 | $0.02610 |
| Opus 5 | $0.00034 | $0.01305 |
| Sonnet 5 | $0.00013 | $0.00522 |
| Haiku 4.5 | $0.00007 | $0.00261 |
Grade A, and why
pg-io-deep-dive 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 8d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL I/O Deep-Dive
This skill guides a thorough investigation of PostgreSQL I/O performance using the full capabilities of the analyze_disk_io_patterns tool, correlating I/O data with query workload and configuration.
When to Use This Skill
Use this skill when the user:
- Reports high disk I/O or slow disk performance
- Sees queries with high
blks_reador low cache hit ratios - Reports
temp_blks_writtenin slow queries (work_mem too low) - Sees frequent checkpoint warnings in PostgreSQL logs
- Has "IO" wait events from
analyze_wait_events - Asks "why is my database doing so much disk I/O?"
- Is sizing storage or evaluating SSD vs HDD performance
MCP Resources Available
pgtuner://health/cache-- Quick cache hit ratio check (lightweight, no full health scan)pgtuner://settings/memory-- Current memory configurationpgtuner://settings/checkpoint-- Current checkpoint configurationpgtuner://table/{schema}/{table_name}/stats-- Table-level I/O statistics
Related MCP Prompt
This skill extends the I/O analysis portions of the health_check and diagnose_slow_queries MCP Prompts.
Prerequisites
- The pgtuner-mcp server must be connected with a valid
DATABASE_URI - PostgreSQL 12+ required. PostgreSQL 16+ recommended for
pg_stat_iometrics.
Agent Decision Tree: Where to Start
Is the I/O problem...
|
+--> GENERAL (overall slow, high iowait)?
| --> Start with Step 1 (Buffer Pool) then Step 5 (Checkpoints)
|
+--> QUERY-SPECIFIC (one slow query with high blks_read)?
| --> Start with Step 2 (Table I/O) then Step 3 (Index I/O)
|
+--> TEMP-FILE RELATED (sort/hash spilling to disk)?
| --> Start with Step 4 (Temp Files)
|
+--> CHECKPOINT RELATED (log warnings about checkpoints)?
| --> Start with Step 5 (Checkpoints)
|
+--> UNKNOWN?
--> Start with Step 1 (Buffer Pool) for overall picture
I/O Investigation Workflow
Step 1: Buffer Pool Analysis
Tool: analyze_disk_io_patterns
Parameters:
analysis_type: "buffer_pool"
top_n: 20
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.
- 8d ago First seen · 311 lines · 67 tokens per session scan A a902ecf51063
pg-io-deep-dive is a skill published in the GitHub repository isdaniel/pgtuner_mcp (29 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 2,610 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.