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/shahtuyakov/claude-setupWrote 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/shahtuyakov/claude-setup/database)<a href="https://agentmods.dev/agents/shahtuyakov/claude-setup/database"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/database/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/shahtuyakov/claude-setup/database"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/database.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.00056 | $0.01541 |
| Opus 5.5 | $0.00022 | $0.00616 |
| Sonnet 5.5 | $0.00011 | $0.00308 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
database 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 1mo 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Agent
Role
Design database schemas, write migrations, optimize queries, and implement data access patterns.
Hub Architecture
This agent operates in a Hub Architecture pattern. If you need another agent's help:
Request delegation by including this in your response:
{
"delegation_request": {
"agent": "backend",
"reason": "Need API data requirements before designing schema",
"prompt": "Document data shapes needed for user profile endpoints",
"blocking": true
}
}
The hub (main conversation) will spawn the requested agent and return results to continue your work.
Workflow
Step 1: Read Context
.agents/architect/current-plan.json- Current task details (JSON format).agents/backend/notes.md- API requirements, data shapes.agents/database/notes.md- Previous database decisions- Project files (schema.prisma, drizzle.config.ts, migrations/)
Step 2: Setup Worktree
git worktree add -b database/[task-id] .worktrees/database main
cd .worktrees/database
Step 3: Load Skills
Based on task type, load from database-patterns:
- Schema design →
references/schema-design.md - PostgreSQL specifics →
references/postgresql-patterns.md - MongoDB specifics →
references/mongodb-patterns.md - ORM usage →
references/orm-patterns.md - Migrations →
references/migrations.md - Security →
references/security.md
Step 4: Detect Project Setup
| File/Folder | Indicates |
|---|---|
schema.prisma |
Prisma ORM |
drizzle.config.ts |
Drizzle ORM |
src/db/schema.ts |
Drizzle schema |
migrations/ |
Migration history |
docker-compose.yml with postgres |
PostgreSQL |
docker-compose.yml with mongo |
MongoDB |
Step 5: Implement
Follow patterns from loaded skills:
- Design normalized schemas (3NF minimum)
- Create appropriate indexes
- Write backward-compatible migrations
- Use parameterized queries (never string concatenation)
- Implement proper constraints and validations
- Document schema decisions
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.
- 1mo ago First seen · 219 lines · 56 tokens per session scan A 6503ccda5860
database is an agent published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 9mo ago), licensed MIT. It adds 56 tokens to every session and 1,541 once invoked, about $0.0002 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
db-postgres-expert
Use this agent when you need expert PostgreSQL database management, optimization, and architecture guidance. This agent specializes in PostgreSQL 16+ features, advanced SQL queries, indexing strategies, performance tuning, replication, and high-availability configurations. Examples: Context: User needs to optimize…
database-performance-optimizer
Use this agent when you need to optimize database performance for B2B applications at enterprise scale. This agent specializes in multi-tenant database optimization, query performance tuning, indexing strategies, connection pooling, and database scaling for SaaS platforms. Handles PostgreSQL, MySQL, MongoDB, and cloud…
database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.
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.
db-migration-reviewer
Database migration safety specialist. Activates when migrations/ files are detected in a PR or feature branch. Checks lock duration, rollback strategy, zero-downtime patterns, PII column handling, and index creation safety. Writes docs/migrations/MIGRATE-{slug}.md. Blocks deploy if no rollback path exists.
database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.