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/isdaniel/pgtuner_mcp/pg-connection-analysisnpx skills add isdaniel/pgtuner_mcp --skill pg-connection-analysisgit 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-connection-analysis)<a href="https://agentmods.dev/skills/isdaniel/pgtuner_mcp/pg-connection-analysis"><img src="https://agentmods.dev/badge/skills/isdaniel/pgtuner_mcp/pg-connection-analysis.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.1 | $0.00057 | $0.02102 |
| Opus 5 | $0.00028 | $0.01051 |
| Sonnet 5 | $0.00011 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
pg-connection-analysis 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 5d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL Connection Analysis
This skill guides analysis and optimization of PostgreSQL connection usage using pgtuner-mcp tools.
When to Use This Skill
Use this skill when the user:
- Reports "too many connections" errors or connection refused
- Asks about connection pooling or PgBouncer setup
- Sees high connection counts in monitoring
- Reports idle connections consuming resources
- Asks "how many connections is my database using?" or "do I need a connection pooler?"
- Reports memory pressure related to per-connection overhead
MCP Resources Available
pgtuner://health/connections-- Quick connection utilization check (lightweight)pgtuner://settings/connections-- Connection-related configuration
Related MCP Prompt
This skill supplements the health_check MCP Prompt's connection dimension.
Prerequisites
- The pgtuner-mcp server must be connected with a valid
DATABASE_URI
Agent Decision Tree
What is the user's symptom?
|
+--> "Too many connections / connection refused"
| --> Start with Step 1 (Connection State Breakdown), urgent
|
+--> "Should I use connection pooling?"
| --> Start with Step 1, then Step 3 (Pooling Analysis)
|
+--> "Idle connections eating memory"
| --> Start with Step 1 (focus on idle), then Step 4 (Configuration)
|
+--> "General connection health question"
--> Start with Quick Check (MCP Resource), then Step 1 if needed
Connection Analysis Workflow
Quick Check: Use MCP Resource First
Before running full tool queries, the agent can read the lightweight resource:
Read resource: pgtuner://health/connections
This provides the connection utilization ratio without running the full health check tool. If this shows > 80% utilization, proceed with the full workflow.
Step 1: Connection State Breakdown
Tool: get_active_queries
Parameters:
include_idle: true
include_system: true
min_duration_seconds: 0
Categorize all connections:
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.
- 5d ago First seen · 249 lines · 57 tokens per session scan A 71fb6231ee27
pg-connection-analysis is a skill published in the GitHub repository isdaniel/pgtuner_mcp (28 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 2,102 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.