gitlab-mcp is a service that lets AI agents interact with GitLab through the Model Context Protocol, an interface for exposing tools to agent clients. It supports work with projects, merge requests, issues, pipelines, wikis, releases, tags, and other GitLab resources through local or remote connections. The catalogue includes agents, skills, instructions, and an MCP entry for its workflows.
Borrowing it
Nothing to install: this file belongs to zereight/gitlab-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zereight/gitlab-mcp/main/.github/agents/database-reviewer.agent.mdgit clone --depth 1 https://github.com/zereight/gitlab-mcpWrote 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/zereight/gitlab-mcp/database-reviewer)<a href="https://agentmods.dev/agents/zereight/gitlab-mcp/database-reviewer"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/database-reviewer/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/zereight/gitlab-mcp/database-reviewer"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/database-reviewer.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.00041 | $0.01852 |
| Opus 5.5 | $0.00016 | $0.00741 |
| Sonnet 5.5 | $0.00008 | $0.00370 |
| Haiku 4.5 | $0.00004 | $0.00185 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- database-reviewer — 100% identical, 0 lines differ
- database-reviewer — 91% identical, 4 lines differ
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 ANALYZEin PostgreSQL,EXPLAINin 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
WHEREpattern (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.
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 · 141 lines · 41 tokens per session scan A 5290de8a60b2
database-reviewer is an agent published in the GitHub repository zereight/gitlab-mcp (2,047 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,852 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
database-reviewer
Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".
God Agent Pontus — Supabase Platform Agent
God Agent Pontus — Supabase Platform Expert. Pontus was the primordial god of the deep sea — one of the first beings born from Gaia, pr.
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
code-reviewer
Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.