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 tallclub/matimo --skill postgres-dbagit clone --depth 1 https://github.com/tallclub/matimoWrote 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/tallclub/matimo/postgres-dba)<a href="https://agentmods.dev/skills/tallclub/matimo/postgres-dba"><img src="https://agentmods.dev/badge/skills/tallclub/matimo/postgres-dba/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/tallclub/matimo/postgres-dba"><img src="https://agentmods.dev/badge/skills/tallclub/matimo/postgres-dba.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.01759 |
| Opus 5.5 | $0.00041 | $0.00704 |
| Sonnet 5.5 | $0.00021 | $0.00352 |
| Haiku 4.5 | $0.00010 | $0.00176 |
Grade A, and why
postgres-dba 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 2mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL DBA Skill
A complete skill for DBA agents to monitor, diagnose, and manage PostgreSQL databases using Matimo tools.
Prerequisites
All tools communicate with PostgreSQL via a REST API wrapper. Ensure:
- A REST API (PostgREST, custom Express/FastAPI, or Supabase) is running and accessible.
- Two environment variables are set:
PG_API_URL— Base URL of the REST API (e.g.,http://localhost:3000)PG_API_KEY— Bearer token for authenticating with the REST API
The API must expose a POST /query endpoint accepting { sql, database } and returning { rows, rowCount, fields }.
Tools You Will Use
| Tool | Purpose |
|---|---|
pg_run_query |
Execute arbitrary read-only SQL SELECT statements |
pg_table_stats |
Get table size, live/dead row counts, and VACUUM history |
pg_slow_queries |
Fetch top slow queries from pg_stat_statements |
pg_index_health |
Inspect index usage stats and identify unused indexes |
pg_active_connections |
Monitor live connections and long-running transactions |
pg_vacuum_status |
Check dead tuple counts and autovacuum status per table |
Workflow 1: Health Check (Start Here)
When a user asks "how is my database doing?", run this sequence:
Step 1 — Active Connections Snapshot
pg_active_connections({ state: "all", minDurationSeconds: 0 })
Look for: high connection count, idle in transaction states, long-running queries (duration > 30s).
Step 2 — Table Health Overview
pg_table_stats({ schema: "public" })
Look for: high dead_rows relative to live_rows, missing recent last_autovacuum timestamps.
Step 3 — VACUUM Pressure Check
pg_vacuum_status({ schema: "public", deadTupleThreshold: 5000 })
Look for: dead_pct above 10%, stale last_autovacuum on high-write tables.
Step 4 — Index Health
pg_index_health({ schema: "public", showUnused: true })
Look for: large indexes with 0 scans (storage waste and write overhead).
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.
- 2mo ago First seen · 206 lines · 103 tokens per session scan A 57c935c6ee3a
postgres-dba is a skill published in the GitHub repository tallclub/matimo (18 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,759 once invoked, about $0.0004 per session on Opus 5.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.
postgres-dba compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| postgres-dbatallclub/matimo | Skill | 18 | yesterday | MIT | A | 103 | Claude Code, Codex |
| alloydb-basicsgoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 72 | Claude Code, Codex |
| postgresql-table-designwshobson/agents | Skill | 42k | yesterday | MIT | A | 37 | Claude Code |
| db-repairgarrytan/gbrain | Skill | 32k | today | MIT | A | 96 | Claude Code |
| volcengine-rds-postgresqlbytedance/agentkit-samples | Skill | 484 | today | Apache-2.0 | A | 63 | Claude Code, Codex |
| dsqlawslabs/agent-plugins | Skill | 937 | yesterday | Apache-2.0 | A | 246 | Claude Code |
| analyzing-insights-across-teamsPostHog/posthog-foss | Skill | 728 | yesterday | MIT | A | 115 | Claude Code, Codex |