database

A database development agent for storing and retrieving application data. It works with PostgreSQL, MongoDB, Prisma, and Drizzle ORM, which is a code layer for working with databases.

In plain words
What is it for?
Use it to design schemas, write migrations, optimize queries, choose indexes, configure an ORM, and implement data access.
Why use it?
It helps plan how data is organized and address slow or difficult database operations before they cause problems in the application.

Agent

Install

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.

agentmods
npx agentmods add agents/shahtuyakov/claude-setup/database
Clone the repo
git clone --depth 1 https://github.com/shahtuyakov/claude-setup
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.01541
Opus 5 $0.00028 $0.00771
Sonnet 5 $0.00011 $0.00308
Haiku 4.5 $0.00006 $0.00154

Measured 2d ago against content hash 6503ccda5860, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

agents/database.md · 219 lines

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

Read the full file on GitHub · 219 lines

Changes

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.

  1. 2d ago First seen · 219 lines · 56 tokens per session scan A 6503ccda5860

Subscribe to this mod's changes

database is an agent published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 1,541 once invoked, about $0.0003 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.