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 commands/sgaunet/claude-plugins/analyze-db-performancegit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/analyze-db-performance)<a href="https://agentmods.dev/commands/sgaunet/claude-plugins/analyze-db-performance"><img src="https://agentmods.dev/badge/commands/sgaunet/claude-plugins/analyze-db-performance.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.00014 | $0.01666 |
| Opus 5 | $0.00007 | $0.00833 |
| Sonnet 5 | $0.00003 | $0.00333 |
| Haiku 4.5 | $0.00001 | $0.00167 |
Grade A, and why
analyze-db-performance 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Database Performance Command
Analyze PostgreSQL database performance using pg_stat_statements, slow query logs, and system metrics.
Process
-
Validate Input: Check if argument is:
- Database connection string (postgres://...)
- Path to slow query log file
- None (will look for local log files)
-
Gather Performance Data: Launch 3 parallel Haiku agents to collect database metrics concurrently:
Agent #1: Slow Query Analyzer
- If connection string: Execute query against pg_stat_statements
SELECT query, calls, total_exec_time, mean_exec_time, max_exec_time FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 20; - If log file: Parse slow query log and extract patterns
- Return: list of top 20 slowest queries with execution stats
Agent #2: Table Size Analyzer
- If connection string: Execute table size query
SELECT schemaname, tablename, pg_size_pretty(pg_total_relation_size(schemaname||'.'||tablename)) FROM pg_tables ORDER BY pg_total_relation_size(schemaname||'.'||tablename) DESC; - Return: list of tables sorted by size
Agent #3: Index Usage Analyzer
- If connection string: Execute index usage query
SELECT schemaname, tablename, indexname, idx_scan FROM pg_stat_user_indexes WHERE idx_scan = 0 ORDER BY pg_relation_size(indexrelid) DESC; - Return: list of unused indexes (candidates for removal)
- If connection string: Execute query against pg_stat_statements
-
Launch 2 parallel Sonnet agents to analyze performance data:
Agent #4: PostgreSQL Specialist (
postgresql-specialistagent)- Analyze slow queries from Agent #1
- Review table sizes from Agent #2
- Evaluate index usage from Agent #3
- Generate optimization recommendations specific to PostgreSQL
- Return: PostgreSQL-specific findings (indexes, query rewrites, config tuning)
Agent #5: General Database Specialist (
database-specialistagent)- Perform cross-platform analysis of performance patterns
- Identify anti-patterns (N+1 queries, missing indexes, bloat)
- Suggest architectural improvements
- Return: general database optimization recommendations
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 · 190 lines · 14 tokens per session scan A a780c3bd134e
analyze-db-performance is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,666 once invoked, about $0.0001 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 commands, from other repositories
write-query
Generate SQL queries from natural language — supports BigQuery, PostgreSQL, MySQL, and more.
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.