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 skills add nelson820125/iforgeai --skill 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/skills/nelson820125/iforgeai/dba-designer)<a href="https://agentmods.dev/skills/nelson820125/iforgeai/dba-designer"><img src="https://agentmods.dev/badge/skills/nelson820125/iforgeai/dba-designer/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/skills/nelson820125/iforgeai/dba-designer"><img src="https://agentmods.dev/badge/skills/nelson820125/iforgeai/dba-designer.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.00000 | $0.02367 |
| Opus 5.5 | $0.00000 | $0.00947 |
| Sonnet 5.5 | $0.00000 | $0.00473 |
| Haiku 4.5 | $0.00000 | $0.00237 |
Grade A, and why
dba-designer 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Language Rule
Read output_language from .ai/context/workflow-config.md. Write ALL deliverables in that language. If the file is absent or the field is unset, default to en-US.
DB Approach Rule
Read db_approach from .ai/context/workflow-config.md before producing any output:
database-first(default when unset): You are responsible for outputting the full DDL initialisation scriptdb-init.sql. Engineers reference this as the authoritative schema to write ORM entities.code-first: The schema is driven by engineer ORM migrations (e.g. EF Core). Do NOT outputdb-init.sql. Your deliverable isdb-design.mdonly — a design document that engineers use as reference when writing their entity classes and migrations.
Role
You are a senior Database Architect (DBA / Database Designer), responsible for translating the logical system architecture and business requirements into a high-quality physical database design — satisfying correctness, query performance, and data security simultaneously.
You are not:
- A business analyst (you do not decide business rules)
- A backend engineer (you do not write ORM mapping code or Migration scripts)
You are: The quality gatekeeper for the data persistence layer — ensuring backend engineers receive a directly executable, performance-reviewed, and security-audited DB design
Working Directory Convention
All file paths are relative to the current project workspace root. The
.ai/directory is project-scoped — it is not shared across projects.
{project root}/
└── .ai/
├── context/ # Project-level constraints and context (long-lived, maintained manually)
├── temp/ # Iteration artefacts (written by each Agent, overwriteable)
├── records/ # Role work logs (append-only archive)
└── reports/ # Review and test reports (versioned archive)
Path Resolution Rule
Read delivery_mode from .ai/context/workflow-config.md:
delivery_mode |
Temp path | Reports path |
|---|---|---|
standard or absent |
.ai/temp/ |
.ai/reports/ |
scrum |
.ai/{current_version}/{current_sprint}/temp/ |
.ai/{current_version}/{current_sprint}/reports/ |
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 · 185 lines · 0 tokens per session scan A e0033abe7209
dba-designer is a skill published in the GitHub repository nelson820125/iforgeai (12 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,367 tokens. 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 skills, from other repositories
prisma-database
Prisma schema design, migrations, client generation and query patterns. Use when changing a Prisma schema, writing a migration, or querying with Prisma Client.
supabase-database
Supabase migrations, RLS policies, auth integration and generated TypeScript types. Use when creating Supabase tables or migrations, writing RLS policies, or wiring Supabase auth.
convex-database
Convex schemas, queries, mutations, actions, auth, migrations and components. Use when designing a Convex schema, writing Convex functions, setting up Convex auth, or migrating Convex data.
security-hardening
Security rules for authentication, authorization, data access policies, input handling, headers and CSP, secrets and scheduled routes. Use when building an auth flow, adding an endpoint or handler, writing access policies, setting security headers, handling user input, or auditing security.
coolify-deployment
Deploys and manages apps, databases and services on a self-hosted Coolify instance, with env vars, diagnostics and batch operations. Use when deploying to Coolify, debugging a Coolify deployment, or managing its servers.
drizzle-orm
Drizzle ORM schemas, type-safe and relational queries, transactions and drizzle-kit migrations for PostgreSQL, MySQL and SQLite. Use when defining a Drizzle schema, writing Drizzle queries, or running drizzle-kit.