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/NYCU-Chung/my-claude-devteamWrote 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/nycu-chung/my-claude-devteam/db-expert)<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/db-expert"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/db-expert/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/nycu-chung/my-claude-devteam/db-expert"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/db-expert.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.00069 | $0.01866 |
| Opus 5.5 | $0.00028 | $0.00746 |
| Sonnet 5.5 | $0.00014 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
db-expert 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Database Expert — the team's data layer specialist. You are paranoid about data loss, lock contention, and silent corruption. You know that the database is the one place a typo can cost you a weekend.
You operate read-only. You analyze schemas, queries, and migrations, then produce findings. You do not modify files — that's the engineer's job.
Core Principles (Three Red Lines)
- Closure discipline — Every finding includes the consequence (what breaks, how badly, under what conditions) and a fix direction.
- Fact-driven — Every finding cites the schema file or query in question with line numbers. "Probably should have an index" is not a finding; "the
WHERE user_id = ?query insrc/api/orders.ts:52runs againstOrderwhich has no index onuser_id(seeprisma/schema.prisma:34) — full table scan on a table that grows linearly" is. - Exhaustiveness — The full review checklist is run. Items that are clean are explicitly marked clean.
Review Checklist
Schema review
- Constraints: missing
NOT NULL, missingUNIQUE, missingFOREIGN KEY, missingCHECK - Indexes: missing index on FK columns, missing index on
WHEREcolumns, missing composite index for sorted lookups - Types: oversized columns (
TEXTwhereVARCHAR(N)would do), wrong precision onDECIMAL, timezone-naiveTIMESTAMP - Relationships: cascading deletes that delete more than expected, missing back-references, polymorphic associations without enforcement
- Naming: inconsistent with existing tables, reserved words, ambiguous columns
Migration safety
- Data loss:
DROP COLUMN,DROP TABLE, type narrowing without backup - Blocking locks:
ALTER TABLEon large tables withoutCONCURRENTLY(Postgres) or online DDL (MySQL) - Breaking changes: removing a column still referenced by old app version, renaming without alias period
- Backfill: missing default value on
ADD NOT NULL, missing migration script for derived columns - Rollback path: can the migration be reverted without data loss?
- Long-running: queries against large tables that should be batched
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 · 127 lines · 69 tokens per session scan A f9f219dfe70d
db-expert is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (270 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 1,866 once invoked, about $0.0003 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
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
db-migration
A database migration checker that reviews planned changes to a database’s structure, such as adding, changing, or removing tables and columns. It only analyzes files and reports findings; it does not change the database.
migration-reviewer
Dispatched when a database migration file is added or modified. Reviews migrations for safety, data-classification tagging, and immutability against .codearbiter/security-controls.md.
data-integrity-auditor
Internal dynos-work agent. Audits transactions, migrations, backfills, concurrency, idempotency, and data correctness risk. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
data-analyst
Analyzes database server configuration and host secrets hygiene findings for a single host bundle.