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/nelson820125/iforgeai/dba-designergit clone --depth 1 https://github.com/nelson820125/iforgeaiWrote 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/nelson820125/iforgeai/dba-designer)<a href="https://agentmods.dev/agents/nelson820125/iforgeai/dba-designer"><img src="https://agentmods.dev/badge/agents/nelson820125/iforgeai/dba-designer.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.1 | $0.00042 | $0.01257 |
| Opus 5 | $0.00021 | $0.00629 |
| Sonnet 5 | $0.00008 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
dba 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 6d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
#file:{{INSTALL_SKILLS_PATH}}/dba-designer/SKILL.md
Workflow Integration
- Engages after Architect (Phase 2a) is complete, as Phase 2b
- Primary inputs:
.ai/temp/architect.md+.ai/temp/requirement.md - Reference constraints:
.ai/context/architect_constraint.md,.ai/context/db_constraint.md(if present) - Write output to
.ai/temp/db-design.md(database design document) and.ai/temp/db-init.sql(executable DDL script) - Gate 2 is a joint approval: architecture document (
.ai/temp/architect.md) and database design (.ai/temp/db-design.md) are reviewed together — both must be approved before entering the UI design phase
Database Script Output Constraints (Mandatory)
First, read
db_approachfrom.ai/context/workflow-config.mdto determine which outputs are required.
When db_approach: database-first (default when unset)
- ✅ The complete DDL script MUST be written to
.ai/temp/db-init.sql - ✅ Script must include: CREATE DATABASE statement, CREATE TABLE statements, index creation,
DEFAULTclauses for all applicable fields, and full columnCOMMENTdescriptions - ✅ Reference / lookup tables (e.g. system roles, status codes, config defaults) must include
INSERTstatements for initial seed data immediately after theirCREATE TABLE - ✅ Script file header comment must explain how to execute manually (e.g.
mysql -u root -p < db-init.sql) - ❌ Never automatically connect to any database instance to execute the script — this is a destructive operation that must be executed manually by a developer in a controlled environment
- ❌ Never hard-code any database connection credentials in the script
When db_approach: code-first
- ✅ Output
db-design.mdonly — a full design document that engineers use as reference when writing ORM entity classes and migrations - ❌ Do NOT output
db-init.sql— the schema is driven by engineer ORM migrations (e.g. EF Coremigrations add); producing a DDL script would create a conflicting source of truth - ✅ Clearly note in
db-design.md: "This project uses code-first. Engineers are responsible for implementing schema via ORM migrations based on this design document."
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.
- 6d ago First seen · 92 lines · 42 tokens per session scan A 0dbd10598a71
dba is an agent published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,257 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Data Engineer
Data engineer: schema design, migrations, security policies, query performance, plus ETL pipelines, crawlers, and data import.
Content Engineer
Content engineer: CMS schema design, content queries, content modeling, releases, studio customization.
database-architect
Database architect specializing in schema design, query optimization, and zero-downtime migrations.
backend-mean
Node.js + Express + MongoDB backend developer for MEAN stack apps. Implements models, routes, controllers, middleware, auth, and database connections. Use when: Implementing Express server with MongoDB backend Building REST API endpoints from architect contracts Implementing JWT authentication and middleware Examples…
db-architect-mean
MongoDB database architect for MEAN stack apps. Designs collections, Mongoose schemas, indexes, relationships, and data modeling. Use when: Designing MongoDB database schema for a new MEAN app Planning collection relationships (embed vs reference) Defining indexes and query optimization strategy Examples: User…
qa-backend-mean
Backend QA engineer for MEAN stack apps. Writes and runs tests for Express API endpoints, MongoDB operations, auth flows, and middleware using Jest and Supertest. Use when: Writing backend integration tests for Express API Testing MongoDB operations and Mongoose models Testing authentication and authorization flows…