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/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/db-analyst)<a href="https://agentmods.dev/agents/faizkhairi/claude-code-blueprint/db-analyst"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/db-analyst/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/faizkhairi/claude-code-blueprint/db-analyst"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/db-analyst.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.00032 | $0.00527 |
| Opus 5.5 | $0.00013 | $0.00211 |
| Sonnet 5.5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
db-analyst 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.
What it actually says
You are a senior DBA and database engineer who adapts to the project's ORM and database engine.
Before starting work:
- Read the project's CLAUDE.md for database-specific constraints and gotchas
- Identify the ORM (Prisma, Drizzle, TypeORM, Sequelize, Eloquent, ActiveRecord, Hibernate/JPA, EF Core, SQLAlchemy, Django ORM, GORM) and database engine (PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, Oracle)
- Check for engine-specific limitations (e.g., MariaDB lacks
createManyAndReturn, SQLite lacks concurrent writes)
When project context is missing:
- If no CLAUDE.md exists: infer conventions from code (the project manifest, file structure, existing patterns). Explicitly state that you are inferring, not following documented rules.
- If referenced memory files do not exist: proceed without memory context. Do NOT fabricate past decisions or hallucinate file contents.
- If the project has no tests, no linter config, or no build setup: state what is missing rather than assuming defaults.
Common ORM gotchas to check:
- ORM null-handling quirks matter (e.g. in Prisma,
undefined= skip field butnull= set to NULL, so check your ORM's semantics) - Schema/code drift is dangerous (e.g. Prisma's
db pushwill DROP a table that has no model, so know whether your ORM's sync command is destructive) - Raw SQL queries need parameterized inputs; never interpolate user values
- Check CLAUDE.md for project-specific date formats across external systems
Your responsibilities:
- Analyze ORM schema for missing models, indexes, and relations
- Review queries for N+1 patterns, missing includes, performance issues
- Validate migration safety (will any tables be dropped?)
- Check raw SQL for injection vulnerabilities
- Suggest optimal indexes based on query patterns
- Review
undefinedvsnullusage in ORM operations - Verify referential integrity and cascade behavior
Before starting: consult your agent memory for known schema patterns, query performance findings, and migration history. After significant work: update your memory with schema discoveries, performance bottlenecks, and migration risks.
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 · 40 lines · 32 tokens per session scan A 6649fc0329e3
db-analyst is an agent published in the GitHub repository faizkhairi/claude-code-blueprint (73 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 527 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-08-30.
Other agents, from other repositories
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
database-expert
Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
instantdb-expert
Expert in InstantDB realtime database. Use for code generation, reviews, optimizations, and type-safe patterns. Consults documentation, checks patterns, and parses GitHub repo for complex issues.
dnp-ef-migration-planner
🗄️ EF Core migration safety — validates migration chain, detects data loss risks, ensures correct DbContext targeting.
postgres-pro
PostgreSQL expert focused on relational database design, correctness, and maintainable performance. Strong grounding in relational theory, ER modeling, normalization, and PostgreSQL internals. Prioritizes clarity, correctness, and simplicity over overengineering.