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 skills/fattain-naime/engineering-docs/database-design-documentnpx skills add fattain-naime/engineering-docs --skill database-design-documentgit clone --depth 1 https://github.com/fattain-naime/engineering-docsWhat 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.00046 | $0.03277 |
| Opus 5 | $0.00023 | $0.01639 |
| Sonnet 5 | $0.00009 | $0.00655 |
| Haiku 4.5 | $0.00005 | $0.00328 |
Grade A, and why
database-design-document 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 yesterday.
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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce a database design document that specifies the complete logical and physical data model, including entity relationships, table definitions, column constraints, indexing strategy, and migration plan.
Database schema is the hardest type of technical debt to remediate. Changing a column name on a 50M-row table is a 4-hour maintenance window. Designing it correctly upfront is a 2-hour design session.
Input
Works best with: The domain or system being modeled. Also valuable: Business rules, cardinality constraints, known query patterns, performance requirements, existing tables that must integrate.
Example invocation: Design the database schema for PayFlow's merchant management system. Merchants have multiple brands, each with their own settings, domains, and staff users. Users have roles with specific permissions. Brands can have multiple currencies and payment methods.
Key Concepts
Normalization
- 1NF: Atomic values. No repeating groups. Single value per cell.
- 2NF: No partial dependencies. Non-key columns depend on the full primary key.
- 3NF: No transitive dependencies. Non-key columns depend only on the primary key.
- BCNF: Stronger form of 3NF. Every determinant is a candidate key.
- Practical rule: Design to 3NF minimum. Denormalize intentionally and explicitly for performance, with documentation.
Indexing Principles
- Every foreign key column must have an index.
- Columns used in
WHERE,JOIN ON, andORDER BYclauses of hot queries must be indexed. - Composite indexes: column order matters. Most selective column first.
- Never index columns with very low cardinality (e.g., a boolean flag) unless combined with a high-cardinality column.
- Generated stored columns for computed or JSON-extracted values that are queried frequently.
Data Integrity
- Use foreign key constraints for referential integrity - do not enforce at application layer only.
- Use CHECK constraints for value validation where supported.
- Use NOT NULL aggressively. NULL means "unknown" - if a value should always be present, make it NOT NULL.
- Use appropriate data types.
DECIMAL(10,2)notFLOATfor money.DATETIME(6)for timestamps.VARCHAR(255)with deliberate limits, not arbitrary.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 243 lines · 46 tokens per session scan A 1fb82d4a04f8
database-design-document is a skill published in the GitHub repository fattain-naime/engineering-docs (4 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 3,277 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…