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.
git clone --depth 1 https://github.com/fmflurry/settings-opencodeWrote 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/commands/fmflurry/settings-opencode/db-health)<a href="https://agentmods.dev/commands/fmflurry/settings-opencode/db-health"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/db-health/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/commands/fmflurry/settings-opencode/db-health"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/db-health.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.00036 | $0.00433 |
| Opus 5.5 | $0.00014 | $0.00173 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
db-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 27d 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.
What it actually says
DB Health Check Command
Delegate to the postgres-dba agent to run a full read-only instance health battery against this repository's PostgreSQL container (gc-platform-postgres, postgres:16-alpine).
Task
Load the postgres-health-check skill and run the battery: connectivity/uptime, cache hit ratio, dead-tuple/autovacuum hotspots, XID wraparound distance, long-running & idle-in-transaction sessions, unused indexes, checkpoint stats, archiver health, connection count vs max_connections, and the container layer (docker stats, volume presence, healthcheck, shm_size).
Produce a tiered findings report (CRITICAL → HIGH → MEDIUM → LOW) with, per finding: the diagnostic query used, observed values, interpretation (with source URL), severity, and remediation. Mutations (VACUUM, REINDEX, session kills, config changes) appear ONLY as ⚠️ HUMAN CONFIRMATION REQUIRED blocks. Repo changes (compose flags, migrations) are recommended as handoffs to coder via the conductor.
Scope
- If
$ARGUMENTSis provided (e.g.,/db-health vacuum): run only that focus area (vacuum/bloat, connections, wraparound, or indexes) - If
$ARGUMENTSis empty: run the full battery
$ARGUMENTS
Output Format
Return the structured report per the postgres-dba agent specification:
- Severity tiers: CRITICAL → HIGH → MEDIUM → LOW
- Evidence: exact query + observed values per finding
- Remediation: human-confirmation blocks for instance mutations;
coderbriefs for repo changes - Action plan: immediate human steps, then repo-change dispatches, then re-check instruction
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.
- 27d ago First seen · 32 lines · 36 tokens per session scan A 2b7d7b553835
db-health is a command published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 433 once invoked, about $0.0001 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-09-20.
Other commands, from other repositories
trex.db.setup
Start a fresh PostgreSQL container and run all migrations. If a database already exists, this will tear it down first.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
db
Set up or operate Supabase Postgres for this project.
splunk-observability-database-monitoring-setup
Render and validate Splunk Observability Cloud Database Monitoring collector configuration for MongoDB, PostgreSQL, Microsoft SQL Server, MySQL, MariaDB, and Oracle through the Splunk OTel Collector. Keeps secrets out of chat, argv, and rendered files; DB credentials are referenced through Kubernetes Secrets or local…
pg-indexes
Review unused indexes that are safe to drop (pgbot).
rls-plan
Supabase RLS + access-control audit + remediation plan — no SQL until approved.