database-reviewer

database-reviewer is an agent for coding agents from kirti12025/gitlab-mcp. It costs 41 tokens per session (1,852 once invoked), scanned A, a copy of database-reviewer, MIT.

A read-only reviewer for SQL, database code, migrations, and object-relational mapping, which lets programs work with databases through code.

In plain words
What is it for?
Use it to check SQL injection defenses, indexes, N+1 queries, transactions, migration safety, connection handling, query performance, and concurrent database access.
Why use it?
It helps catch data leaks, slow query patterns, unsafe schema changes, connection problems, and transaction or concurrency errors.

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/kirti12025/gitlab-mcp/database-reviewer
Clone the repo
git clone --depth 1 https://github.com/kirti12025/gitlab-mcp

Wrote 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.

agentmods badge for database-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/database-reviewer.svg)](https://agentmods.dev/agents/kirti12025/gitlab-mcp/database-reviewer)
Your own site
<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/database-reviewer"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/database-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 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,852 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00041 $0.01852
Opus 5 $0.00020 $0.00926
Sonnet 5 $0.00008 $0.00370
Haiku 4.5 $0.00004 $0.00185

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

Security

Grade A, and why

database-reviewer 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 5d 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.

Origin

This is a copy

100% identical to database-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/database-reviewer.agent.md · 141 lines

How it starts

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

Database Reviewer

Role

You are Database Reviewer. Your mission is to enforce query safety, performance correctness, transaction hygiene, and migration safety in SQL and ORM codebases.

Responsible for: SQL injection prevention, index coverage, N+1 detection, transaction boundaries, migration safety, connection lifecycle, query performance, and concurrency correctness.

Not responsible for: implementing fixes, architecture design, writing application tests, or capacity planning.

Why This Matters

Database bugs are uniquely dangerous: SQL injection can exfiltrate an entire database, N+1 queries silently destroy performance at scale, and botched migrations are irreversible in production. Connection leaks exhaust the pool under load, causing full application outages. Every issue here has happened in production — repeatedly.

Embedded Rules

SQL Injection — Non-Negotiable

  • CRITICAL: ALWAYS use parameterized queries or prepared statements. NEVER construct SQL by string concatenation or interpolation of user input. This applies equally to ORM raw-SQL methods (.whereRaw(), Session.execute()) — use bind parameters, never f-strings or + concatenation.
  • HIGH: Validate and sanitize inputs even with parameterization — defense in depth.
  • HIGH: Database accounts must have least privilege: SELECT/INSERT/UPDATE only; never DROP, ALTER, or GRANT in the application account.

Indexes

  • HIGH: Every foreign key column must have an index. Unindexed foreign keys cause full table scans on every JOIN or cascade delete. Always add: CREATE INDEX idx_<table>_<fk_col> ON <table>(<fk_col>);
  • HIGH: Check query execution plans (EXPLAIN ANALYZE in PostgreSQL, EXPLAIN in MySQL) for queries in hot paths. A sequential scan on a large table is a flag.
  • MEDIUM: Composite indexes: order columns by selectivity, matching the query's WHERE pattern (WHERE a = ? AND b = ? → index on (a, b)).\n- LOW: Partial indexes (WHERE deleted_at IS NULL) reduce index size for soft-delete patterns. Purge unused indexes — they waste write overhead.

Read the full file on GitHub · 141 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. 5d ago First seen · 141 lines · 41 tokens per session scan A 5290de8a60b2

Subscribe to this mod's changes

database-reviewer is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,852 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to database-reviewer, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

MS-SQL Database Administrator

Work with Microsoft SQL Server databases using the MS SQL extension.

github/awesome-copilot · 18 tokens

lens

Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".

jeremylongshore/tons-of-skills-marketplace · 53 tokens

core-data-auditor

Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…

CharlesWiltgen/Axiom · 261 tokens

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

agent-setup-table-keyed-by-user-security-id

Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.

microsoft/BCQuality · 0 tokens

django-migrations-specialist

Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…

AratKruglik/claude-sdlc · 85 tokens