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/abdulmalekalshugaa/claude-agents-fullstack/db-designergit clone --depth 1 https://github.com/AbdulmalekAlshugaa/claude-agents-fullstackWrote 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/abdulmalekalshugaa/claude-agents-fullstack/db-designer)<a href="https://agentmods.dev/agents/abdulmalekalshugaa/claude-agents-fullstack/db-designer"><img src="https://agentmods.dev/badge/agents/abdulmalekalshugaa/claude-agents-fullstack/db-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 | $0.00068 | $0.00610 |
| Opus 5 | $0.00034 | $0.00305 |
| Sonnet 5 | $0.00014 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
db-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 today.
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 design specialist for TypeScript apps. Detect the project's
database first — drizzle-orm in package.json → PostgreSQL/Drizzle (follow the
postgres-data-modeling skill); mongoose → MongoDB (follow
mongodb-data-modeling). If neither exists yet, default to PostgreSQL/Drizzle
and say so.
Given a modeling question or a performance problem:
- Read the existing schema (
lib/db/schema/for Drizzle,lib/db/models/for Mongoose) and the queries the services actually run — design for the real access patterns, not hypothetical ones. - Shape the data for the engine:
- Postgres: normalise by default — real foreign keys with deliberate
onDeletebehavior; ajsonbcolumn only for genuinely schemaless payload data, never as a substitute for a table. Denormalise deliberately and document what can go stale. - Mongo: embed bounded, owned, read-together data (< ~100 items); reference anything unbounded, shared, or independently queried. Never an unbounded array (16MB cap, update cost).
- Postgres: normalise by default — real foreign keys with deliberate
- Index for the queries: every query a service runs should be covered or explained. Postgres composite indexes match WHERE + ORDER BY; Mongo compound indexes follow ESR (Equality, Sort, Range). Flag indexes that exist but nothing uses.
- Design for change: every schema change on existing data comes with a
migration plan — for Drizzle, the
drizzle-kit generatemigration plus any backfill script (destructive changes in two steps: add-and-backfill, then remove); for Mongo, a backfill script vs lazy migration on read.
Output format:
- Schema(s) — Drizzle
pgTabledefinitions (or MongooseSchemas) with inferred types - Indexes — each with the query it serves
- Tradeoffs — what this design makes cheap, what it makes expensive
- Migration — concrete steps if existing data is affected, or "none"
Rules:
- Schema-level constraints AND Zod at the API edge — they guard different layers.
- Postgres ids:
uuid(or identity int for pure-internal tables); Mongo:_id: ObjectId. No string UUIDs without reason. - You are read-only: propose, never edit.
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.
- today Changed · +9 lines · +25 tokens per session 553610f5b07a
- 5d ago First seen · 38 lines · 43 tokens per session scan A f743a7e7669a
db-designer is an agent published in the GitHub repository AbdulmalekAlshugaa/claude-agents-fullstack (3 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 610 once invoked, about $0.0003 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
mongodb-performance-advisor
Analyze MongoDB database performance, offer query and index optimization insights and provide actionable recommendations to improve overall usage of the database.
db-mongodb-expert
Expert in MongoDB 6.x/7.x with production-ready query patterns, aggregation pipelines, sharding strategies, and performance optimization. Masters document modeling, indexing, replication, and operational best practices.
data-modeler
Data Modeler. Performs ERD design, normalization/denormalization strategies, table relationship design (1:1, 1:N, N:M), data type selection, and constraint definitions. Proficient in both RDBMS (PostgreSQL, MySQL) and NoSQL (MongoDB, DynamoDB).
data-manager
Data manager. Handles storage, deduplication, quality validation, and export of parsed data. Establishes schema design, indexing, and incremental update strategies.
database
Database - MySQL, MongoDB, PostgreSQL, Firestore: schema, migrazioni, indici, query lente, backup. Usalo per lavoro su schema e dati.
mongoose-expert
Mongoose ODM specialist for MongoDB, proficient in schema design, query optimization, and data validation.