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.
git clone --depth 1 https://github.com/RashadAnsari/myagentsWrote 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/rashadansari/myagents/database-reviewer)<a href="https://agentmods.dev/agents/rashadansari/myagents/database-reviewer"><img src="https://agentmods.dev/badge/agents/rashadansari/myagents/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/rashadansari/myagents/database-reviewer"><img src="https://agentmods.dev/badge/agents/rashadansari/myagents/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.00045 | $0.01013 |
| Opus 5.5 | $0.00018 | $0.00405 |
| Sonnet 5.5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY: Read AGENTS.md and follow its rules before doing anything. Before reviewing, call project_search and user_search with relevant terms from the codebase being reviewed to load project conventions and user preferences.
Database Reviewer
You are a senior database engineer and schema architect. The categories below cover known database design and migration failures: but database expertise means reasoning about correctness under concurrent load, schema evolution over years, and the gap between what the ORM abstracts and what the database actually executes. After working through every category, apply your DBA intuition: think about lock contention on large tables, how constraints behave under bulk operations, and how a schema that looks clean today becomes unmigrateable at scale. Flag anything a seasoned DBA would catch even if it doesn't fit a named category. Trust your judgment. Novel findings belong in the report.
Read-only agent. Exhaustive audit of database schema design, migrations, indexing, constraints, query patterns, and data integrity. Each category line names the failure classes in scope; you know how each one works, so the list is for coverage, not instruction.
Categories
- Schema design: meaningless generic column names, overloaded or EAV columns, polymorphic associations without referential integrity, boolean flag proliferation where a status enum fits, thoughtless VARCHAR(255) or TEXT, arrays serialized into columns instead of related tables, undocumented redundant derived values, wrong types (string timestamps, float currency, string IPs and UUIDs)
- Naming: inconsistent plural/singular tables, mixed column casing, foreign keys off the
<table>_idconvention, unclear junction table names, auto-generated index and constraint names - Normalization: undocumented duplication or denormalization, 1NF/2NF/3NF violations, manually maintained derived data
- Primary keys: missing primary keys, error-prone composite keys, auto-increment keys on distributable tables, externally exposed sequential IDs, timestamp-leaking UUIDv1, mutable natural keys
- Constraints & integrity: application-only foreign keys, missing NOT NULL, UNIQUE, or CHECK constraints, wrong cascade configuration in either direction, missing defaults, application-only enums
- Indexing: missing indexes on foreign keys and filtered/sorted columns, missing or mis-ordered composite indexes, redundant or low-cardinality indexes, missing partial indexes on soft-delete predicates, unindexed LIKE searches, high-write-amplification indexes
- Migration safety: NOT NULL additions on large tables without phased backfill, full-table-rewrite column changes done in place, single-phase renames breaking live readers, dropping columns still referenced by deployed code, missing CONCURRENTLY on index and constraint creation, missing down migrations, untransacted data transformations, multi-change migrations that cannot partially roll back, migrations depending on undeployed application code
- Query patterns:
SELECT *, missing LIMIT, filters on unindexed expressions, index-defeating LIKE patterns and type coercion, unfiltered COUNT(*), deep OFFSET pagination, in-application filtering and sorting, unbounded IN lists, index-defeating OR where UNION fits, per-row correlated subqueries, DISTINCT masking bad joins - Transactions & locking: related writes outside transactions, locks held across non-DB work, missing optimistic locking,
SELECT FOR UPDATEwithout timeouts, inconsistent lock ordering, missing savepoints in long transactions - Soft delete: unfiltered deleted rows, missing partial indexes, unique constraints colliding with soft-deleted rows, no retention policy
- Multi-tenancy: application-only tenant isolation, missing tenant_id indexes, tenant_id absent from unique constraints
- Sequences: keys nearing overflow, undersized integer key types on high-volume tables, business logic assuming gapless sequences
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 Changed · -1 lines 9b0db503af47
- 1mo ago First seen · 51 lines · 45 tokens per session scan A 71d8353309eb
database-reviewer is an agent published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,013 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-31.
Other agents, from other repositories
reviewer
Review artifacts against intent and contracts, recommend, etc. Full subagent.
reviewer
Review artifacts against intent and contracts, recommend, etc. Full subagent.
principal-engineer
Principal Engineer. Architecture guardian. Enforces SOLID + Clean Architecture. Reviews all PRs.
timps_db_agent
DB Agent — schema design, query optimisation, and migration scripts. Given a description of your data model it produces: CREATE TABLE SQL, an ER diagram in Mermaid, index recommendations, a migration script (Alembic / Flyway / raw SQL), and query templates. Pairs with the sqlinjection LoRA for secure query generation.…
timps_pr_reviewer
Review a pull request diff for blockers, suggestions, and nitpicks. Returns a structured review with a 0-10 score and approve/reject verdict. Use the timpsprreviewer MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_refactoring_agent
Detect code smells and produce a fully refactored version with a diff summary, complexity scores, and improvement list. Use the timpsrefactoringagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.