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 abiswas97/postgres-mcp --skill database-healthgit clone --depth 1 https://github.com/abiswas97/postgres-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/abiswas97/postgres-mcp/database-health)<a href="https://agentmods.dev/skills/abiswas97/postgres-mcp/database-health"><img src="https://agentmods.dev/badge/skills/abiswas97/postgres-mcp/database-health.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.00033 | $0.00180 |
| Opus 5 | $0.00016 | $0.00090 |
| Sonnet 5 | $0.00007 | $0.00036 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
database-health 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- database-health — 100% identical, 0 lines differ
What it actually says
Run the diagnose_database MCP tool to get a composite health assessment.
Interpret results by status:
- critical: Address critical checks immediately. Common actions: kill idle-in-transaction connections, run VACUUM on bloated tables, increase shared_buffers for low cache hit ratio.
- warning: Schedule maintenance. Review unused indexes for removal, check vacuum schedules, monitor connection trends.
- healthy: Confirm health. Note any checks_skipped that may need extension installation.
If slow queries appear in results, offer to run get_slow_queries for deeper analysis. If connection issues appear, offer to run get_connections for per-connection detail. If pg_stat_statements is not installed, suggest enabling it for slow query visibility.
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.
- 7d ago First seen · 16 lines · 33 tokens per session scan A 22e81432df7e
database-health is a skill published in the GitHub repository abiswas97/postgres-mcp (1 stars, last pushed 6mo ago), licensed ISC. It adds 33 tokens to every session and 180 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
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.
django-perf-review
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.