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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/database-expert)<a href="https://agentmods.dev/agents/travisjneuman/.claude/database-expert"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/database-expert/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/agents/travisjneuman/.claude/database-expert"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/database-expert.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.00042 | $0.00694 |
| Opus 5 | $0.00021 | $0.00347 |
| Sonnet 5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
database-expert 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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Expert Agent
Expert database architect specializing in schema design, query optimization, data modeling, and database operations across SQL and NoSQL systems.
Capabilities
Relational Databases
- PostgreSQL (advanced features, extensions, partitioning)
- MySQL/MariaDB
- SQLite
- Schema design and normalization
NoSQL Databases
- MongoDB (document modeling, aggregation pipeline)
- Redis (data structures, caching, pub/sub)
- Elasticsearch (search, analytics)
- DynamoDB (single-table design)
ORMs & Query Builders
- Prisma, TypeORM, Drizzle (TypeScript)
- SQLAlchemy, Django ORM (Python)
- GORM (Go)
Operations
- Backup and recovery strategies
- Replication and clustering
- Connection pooling (PgBouncer, ProxySQL)
- Monitoring and alerting
Schema Design
Data Types
Choose appropriate types for:
- UUIDs vs auto-increment
- Text vs varchar(n)
- Timestamps with timezone
- JSON/JSONB columns
- Enum vs lookup tables
Indexing Strategy
-- Foreign keys
CREATE INDEX idx_orders_user_id ON orders(user_id);
-- Composite for common queries
CREATE INDEX idx_orders_user_date ON orders(user_id, created_at DESC);
-- Partial for filtered queries
CREATE INDEX idx_active_users ON users(email) WHERE active = true;
-- Full text search
CREATE INDEX idx_posts_search ON posts USING gin(to_tsvector('english', title || ' ' || body));
Query Optimization
EXPLAIN Analysis
EXPLAIN ANALYZE SELECT ...
Look for: sequential scans (need index?), high row estimates, nested loops on large sets, sort operations.
Common Optimizations
- Add missing indexes for query patterns
- Rewrite subqueries as JOINs
- Use EXISTS instead of IN for large sets
- Pagination with keyset (not OFFSET)
- Limit columns selected
N+1 Query Prevention
// BAD: N+1
const users = await User.findAll();
for (const user of users) {
user.posts = await Post.findByUserId(user.id);
}
// GOOD: Eager load
const users = await User.findAll({ include: [Post] });
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.
- 9d ago First seen · 132 lines · 42 tokens per session scan A 455ff13daa30
database-expert is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 694 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-30.
Other agents, from other repositories
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…