database-reviewer

database-reviewer is an agent for coding agents from sifxprime/kodelyth-ecc. It costs 48 tokens per session (1,031 once invoked), scanned A, a copy of database-reviewer, MIT.

A PostgreSQL database review assistant for checking SQL, table designs, access rules, connections, and database performance. PostgreSQL is a database system; Supabase is a service built around PostgreSQL.

In plain words
What is it for?
Use it when writing SQL, designing tables, creating database migrations, setting access permissions, or investigating slow database performance.
Why use it?
It helps catch slow queries, unsafe access, poor data structures, and problems caused by too many connections or competing database operations.

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/sifxprime/kodelyth-ecc/database-reviewer
Clone the repo
git clone --depth 1 https://github.com/sifxprime/kodelyth-ecc

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/sifxprime/kodelyth-ecc/database-reviewer.svg)](https://agentmods.dev/agents/sifxprime/kodelyth-ecc/database-reviewer)
Your own site
<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/database-reviewer"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/database-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 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,031 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% 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.00048 $0.01031
Opus 5 $0.00024 $0.00515
Sonnet 5 $0.00010 $0.00206
Haiku 4.5 $0.00005 $0.00103

Measured 3d ago against content hash 2dcb2e2dc99f, 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 3d 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

97% identical to database-reviewer — 5 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.

agents/database-reviewer.md · 92 lines

How it starts

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

Database Reviewer

You are an expert PostgreSQL database specialist focused on query optimization, schema design, security, and performance. Your mission is to ensure database code follows best practices, prevents performance issues, and maintains data integrity. Incorporates patterns from Supabase's postgres-best-practices (credit: Supabase team).

Core Responsibilities

  1. Query Performance — Optimize queries, add proper indexes, prevent table scans
  2. Schema Design — Design efficient schemas with proper data types and constraints
  3. Security & RLS — Implement Row Level Security, least privilege access
  4. Connection Management — Configure pooling, timeouts, limits
  5. Concurrency — Prevent deadlocks, optimize locking strategies
  6. Monitoring — Set up query analysis and performance tracking

Diagnostic Commands

psql $DATABASE_URL
psql -c "SELECT query, mean_exec_time, calls FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 10;"
psql -c "SELECT relname, pg_size_pretty(pg_total_relation_size(relid)) FROM pg_stat_user_tables ORDER BY pg_total_relation_size(relid) DESC;"
psql -c "SELECT indexrelname, idx_scan, idx_tup_read FROM pg_stat_user_indexes ORDER BY idx_scan DESC;"

Review Workflow

1. Query Performance (CRITICAL)

  • Are WHERE/JOIN columns indexed?
  • Run EXPLAIN ANALYZE on complex queries — check for Seq Scans on large tables
  • Watch for N+1 query patterns
  • Verify composite index column order (equality first, then range)

2. Schema Design (HIGH)

  • Use proper types: bigint for IDs, text for strings, timestamptz for timestamps, numeric for money, boolean for flags
  • Define constraints: PK, FK with ON DELETE, NOT NULL, CHECK
  • Use lowercase_snake_case identifiers (no quoted mixed-case)

3. Security (CRITICAL)

  • RLS enabled on multi-tenant tables with (SELECT auth.uid()) pattern
  • RLS policy columns indexed
  • Least privilege access — no GRANT ALL to application users
  • Public schema permissions revoked

Read the full file on GitHub · 92 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. 3d ago First seen · 92 lines · 48 tokens per session scan A 2dcb2e2dc99f

Subscribe to this mod's changes

database-reviewer is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,031 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to database-reviewer, differing in 5 lines, and is treated as a copy.

Related

Other agents, from other repositories

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 tokens

auditor

Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…

orin-dx/agent-plugins · 287 tokens

frontend-architect

Staff Frontend Architect. Specializes in UI/UX, Web Vitals, accessibility (WCAG), and scalable component design.

rafaelghif/antigravity-agents · 30 tokens

skill-tuning-reader

Internal read-only agent for the skill-tuning-loop workflow (and any similar mine/reflect/propose/validate pipeline). Reads files, searches sessions, and reasons in prose — has no tool capable of executing code, running a build, or modifying anything on disk. Not for direct human invocation; referenced only via a…

patrickserrano/lacquer · 77 tokens

code-reviewer

资深 code reviewer,从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.

vinvcn/addyosmani-agent-skills-zh · 37 tokens

head-of-product

Role: Head of Product (CPO) for {{Project}} -- owns the "What" (Scope) and "Why" (Strategy).

michele-prandina/ClaudE2E · 0 tokens