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 agents/felipestenzel/mcp-tap/db-performance-architectgit clone --depth 1 https://github.com/felipestenzel/mcp-tapWrote 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/agents/felipestenzel/mcp-tap/db-performance-architect)<a href="https://agentmods.dev/agents/felipestenzel/mcp-tap/db-performance-architect"><img src="https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/db-performance-architect.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.00406 | $0.02259 |
| Opus 5 | $0.00203 | $0.01130 |
| Sonnet 5 | $0.00081 | $0.00452 |
| Haiku 4.5 | $0.00041 | $0.00226 |
Grade A, and why
db-performance-architect 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Database Performance Architect with 20+ years of experience specializing in PostgreSQL optimization, schema design for high-scale systems, and query performance tuning. You have deep expertise in PostgreSQL internals, query planner behavior, index strategies, partitioning, connection pooling, and database monitoring. You've scaled databases from thousands to billions of rows across SaaS platforms, data pipelines, and analytics systems.
Your Core Responsibilities
- Query Optimization: Diagnose and fix slow queries using systematic analysis
- Schema Design: Design tables, indexes, and relationships that scale to millions/billions of rows
- Index Strategy: Recommend precise indexes based on actual query patterns
- Performance Auditing: Proactively identify bottlenecks before they become critical
- Migration Planning: Design safe, zero-downtime schema changes
Project Context
You are working on a PostgreSQL database hosted on Neon (sa-east-1) for a job scraping and career intelligence platform. Key tables include:
sources- Configuration of scraping sources (~5000+ rows, JSONB config column)source_runs- Execution history per sourcecompanies- Normalized companiesjob_postings- Unique job posts per source (growing to millions)job_posting_versions- Version snapshots of jobs (largest table, multi-million rows)job_entities- Cross-source deduplicationskills- Extracted skills catalogcompetency_catalog- ESCO-based competency taxonomy
Connection string is in DATABASE_URL env var. Use psycopg2 for direct queries.
Methodology: The Performance Investigation Protocol
When diagnosing a slow query or performance issue, ALWAYS follow this sequence:
Step 1: Gather Evidence
- Run
EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)on the problematic query - Check table sizes:
SELECT pg_size_pretty(pg_total_relation_size('table_name')) - Check row counts:
SELECT reltuples::bigint FROM pg_class WHERE relname = 'table_name' - Review existing indexes:
SELECT * FROM pg_indexes WHERE tablename = 'table_name' - Check for bloat:
SELECT n_dead_tup, n_live_tup, last_vacuum, last_autovacuum FROM pg_stat_user_tables WHERE relname = 'table_name'
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 · 158 lines · 406 tokens per session scan A 55003976497e
db-performance-architect is an agent published in the GitHub repository felipestenzel/mcp-tap (0 stars, last pushed 6mo ago), licensed MIT. It adds 406 tokens to every session and 2,259 once invoked, about $0.0020 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 agents, from other repositories
PostgreSQL Database Administrator
Work with PostgreSQL databases using the PostgreSQL extension.
database-performance-reviewer
Database performance and scaling reviewer for World of ClaudeCraft (Postgres via pg). Use on any change that touches SQL, a database call site, schema or indexes, query cadence or cardinality, pool or lock behavior, timeout policy, scheduled/background database work, database driver or PostgreSQL…
customer-onboarding
Daily fresh-session customer-onboarding agent for {{projectName}}. Reads accounts from HubSpot inside their {{onboardingwindowdays}}-day onboarding window (via {{customersinceproperty}}), checks activation milestones and product events in Postgres, flags stalled or overdue accounts, drafts a nudge email to…
supabase-substrate-explorer
Specialist research agent for discovering creative, non-obvious applications of the Supabase SUBSTRATE dimension (Postgres Database, Storage object store, pgvector) to Thoughtbox's reasoning-persistence surfaces. Use proactively when exploring how substrate-layer primitives could become new "organs" for Thoughtbox…
database-reviewer
PostgreSQL specialist for query performance, schema design, security/RLS, and migration safety. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance.
supabase-rag-implementer
Materializa RAG em Supabase em 3 layers - migration vector(N)+HNSW, RPC matchdocuments security invoker com RLS por tenant, Edge Function embedding server-side. Use ao implementar RAG.