db-audit

A command that checks a database schema and the code that queries it for design, performance, and security problems. A database schema defines stored tables and their relationships; indexes help the database find rows faster.

In plain words
What is it for?
Use it to audit indexes, table relationships, queries, or all supported areas, using schema files, migrations, and available live database information.
Why use it?
It can expose missing or unnecessary indexes, broken relationships, inefficient query patterns, and unsafe queries before they cause larger problems.

Command

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 commands/iwritec0de/app-dev/db-audit
Clone the repo
git clone --depth 1 https://github.com/iwritec0de/app-dev
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 785 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.00010 $0.00785
Opus 5 $0.00005 $0.00392
Sonnet 5 $0.00002 $0.00157
Haiku 4.5 $0.00001 $0.00078

Measured yesterday against content hash 0cd2045075d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

db-audit 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 yesterday.

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.

commands/db-audit.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Database Audit

Scan the database schema and codebase for performance, design, and security issues.

Load the database-optimizer and database-designer skills for index analysis and schema design patterns.

Usage

/db-audit [--focus indexes|relations|queries|all]

Arguments

Parse $ARGUMENTS to extract:

  • --focus (optional, default: all) — What to audit
    • indexes — Missing indexes, unused indexes, duplicate indexes
    • relations — Missing foreign keys, orphaned references, cascade issues
    • queries — N+1 patterns, unparameterized queries, full table scans in code
    • all — Run everything

Instructions

1. Gather Schema Information

Read the schema from:

  • ORM schema files (Prisma, TypeORM, Knex, Drizzle, etc.)
  • Migration files
  • MCP database connection (if available — use for live index and stats data)

2. Index Audit

Check for:

  • Missing indexes on foreign keys — Every _id / *_id column should have an index
  • Missing indexes on commonly queried columns — Search code for WHERE clauses and match against indexed columns
  • Composite index opportunities — Queries filtering on multiple columns
  • Unused indexes (if MCP available) — Check pg_stat_user_indexes for zero-scan indexes
  • Duplicate indexes — Indexes that are prefixes of other indexes
  • Missing unique constraints — Columns that should be unique (email, slug, etc.)

3. Relation Audit

Check for:

  • Missing foreign key constraints — Code references user_id but no FK defined
  • Dangerous CASCADE rulesON DELETE CASCADE on tables with important data
  • Orphaned references — FK targets that don't exist
  • Missing NOT NULL — Columns that are always populated but allow NULL
  • Inconsistent naming — Mixed naming conventions (userId vs user_id)

4. Query Audit

Search the codebase for:

  • N+1 query patterns — Queries inside loops, missing eager loading/joins
    # Look for patterns like:
    for user in users:
        posts = db.query("SELECT * FROM posts WHERE user_id = ?", user.id)
    
  • String interpolation in queries — SQL injection risk
    # Dangerous:
    db.query(`SELECT * FROM users WHERE id = ${id}`)
    
  • **SELECT *** — Missing column selection (over-fetching)
  • Missing LIMIT — Unbounded queries
  • Missing transactions — Multi-step writes without transaction wrapping

Read the full file on GitHub · 101 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. yesterday First seen · 101 lines · 10 tokens per session scan A 0cd2045075d8

Subscribe to this mod's changes

db-audit is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 785 once invoked, about $0.0001 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.