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/slow-query-analysisnpx skills add irsyadjpp/postgres-mcp-server --skill slow-query-analysisgit 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/slow-query-analysis)<a href="https://agentmods.dev/skills/irsyadjpp/postgres-mcp-server/slow-query-analysis"><img src="https://agentmods.dev/badge/skills/irsyadjpp/postgres-mcp-server/slow-query-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 | $0.00034 | $0.00209 |
| Opus 5 | $0.00017 | $0.00105 |
| Sonnet 5 | $0.00007 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
slow-query-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 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.
This is a copy
100% identical to slow-query-analysis — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Workflow:
- Run get_slow_queries sorted by total_time to find biggest time consumers
- For the top offender, run explain_query with analyze=true to see the actual execution plan
- Look for: sequential scans on large tables (suggest index), nested loops with high row counts (suggest join rewrite), sorts spilling to disk (suggest work_mem increase or index)
- Check list_indexes on affected tables to see what indexes exist
- Suggest specific actions: CREATE INDEX statements, query rewrites, or configuration changes
If pg_stat_statements is not installed, guide setup:
- Add shared_preload_libraries = 'pg_stat_statements' to postgresql.conf
- Restart PostgreSQL
- Run CREATE EXTENSION pg_stat_statements
- For RDS/Aurora: modify parameter group, reboot instance
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 · 18 lines · 34 tokens per session scan A 6b3c210b1c3b
slow-query-analysis is a skill published in the GitHub repository irsyadjpp/postgres-mcp-server (0 stars, last pushed 28d ago), licensed ISC. It adds 34 tokens to every session and 209 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to slow-query-analysis, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
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…
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.
sql-translate
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.).