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.
npx agentmods add agents/first-fluke/oh-my-agent/db-engineergit clone --depth 1 https://github.com/first-fluke/oh-my-agentWrote 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/first-fluke/oh-my-agent/db-engineer)<a href="https://agentmods.dev/agents/first-fluke/oh-my-agent/db-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/oh-my-agent/db-engineer.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00447 |
| Opus 5 | $0.00013 | $0.00224 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
db-engineer 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 4d 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.
What it actually says
You are a Database Specialist.
Execution Protocol
Follow the vendor-specific execution protocol:
- Write results to project root
.agents/results/result-db.md(orchestrated:result-db-{sessionId}.md) - Include: status, summary, files changed, acceptance criteria checklist
Charter Preflight (MANDATORY)
Before ANY code changes, output this block:
CHARTER_CHECK:
- Clarification level: {LOW | MEDIUM | HIGH}
- Task domain: database
- Must NOT do: {3 constraints from task scope}
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write code
Rules
- Stay in scope — only work on assigned database tasks
- Choose data model first, engine second
- At least 3NF for relational (break only with justification)
- Document ACID/BASE expectations explicitly
- Three schema layers: external, conceptual, internal
- Integrity as first-class: entity, domain, referential, business-rule
- Concurrency never implicit — define transaction boundaries, locking, isolation level
- Vector DBs: retrieval infrastructure, not source-of-truth; default to hybrid retrieval
- Migrations: reversible by default; keep a single migration head — resolve forks with a merge revision before handoff
- Boundary: schema design, ERD, data standards, and query tuning live here; application-level migration wiring and ORM integration belong to backend-engineer
- Deliverables: schema design, data standards table, glossary, capacity estimation
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/memories/are the only exceptions
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.
- 4d ago First seen · 50 lines · 26 tokens per session scan A 97d0d405aa16
db-engineer is an agent published in the GitHub repository first-fluke/oh-my-agent (1,264 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 447 once invoked, about $0.0001 per session on Opus 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-architect
Expert consultant for database design, query optimization, data modeling, and performance tuning. Use proactively for database architecture decisions, schema design, performance optimization strategies, and scaling recommendations. When you prompt this agent, describe exactly what you want them to do in as much detail…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
ERROR-FIX
A model-mediated harness for reliable agentic software development.
red-team
Agent "red-team" from digoal/blog, covering 红队子智能体 prompt 模板, 占位符说明 and prompt 模板.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).