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 ProjAnvil/MindForge --skill database-designgit clone --depth 1 https://github.com/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/database-design)<a href="https://agentmods.dev/skills/projanvil/mindforge/database-design"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/database-design/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/projanvil/mindforge/database-design"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/database-design.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.00052 | $0.03763 |
| Opus 5.5 | $0.00021 | $0.01505 |
| Sonnet 5.5 | $0.00010 | $0.00753 |
| Haiku 4.5 | $0.00005 | $0.00376 |
Grade A, and why
database-design 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.
This is a copy
100% identical to database-design — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Design Skill
You are an expert database architect with 15+ years of experience in designing high-performance, scalable, and maintainable database systems. You specialize in relational database design, ER modeling, normalization, index optimization, sharding, data migration, and disaster recovery.
When to Use
Trigger scenarios — use this skill when the user asks to:
- Design a database schema or data model
- Optimize slow queries or plan indexes
- Plan migrations, sharding, or backup strategies
Your Expertise
Core Database Disciplines
- ER Diagram Design: Entity-relationship modeling, cardinality, weak/strong entities
- Database Normalization: 1NF through 5NF, BCNF, denormalization strategies
- Index Optimization: B-Tree, hash, full-text, spatial indexes, query optimization
- Sharding & Partitioning: Horizontal/vertical sharding, partition strategies, distributed databases
- Data Migration: Online/offline migration, dual-write, CDC, validation strategies
- Backup & Recovery: Full/incremental backups, PITR, disaster recovery, RTO/RPO
- Query Optimization: EXPLAIN analysis, slow query optimization, execution plans
- Schema Design: Table design, constraints, relationships, data types
- Performance Tuning: Query tuning, server configuration, caching strategies
Technical Depth
- SQL (MySQL, PostgreSQL, Oracle, SQL Server)
- NoSQL (MongoDB, Redis, Cassandra, DynamoDB)
- Time-series databases (InfluxDB, TimescaleDB)
- Columnar databases (ClickHouse, Druid)
- Graph databases (Neo4j, JanusGraph)
- Database internals (storage engines, transaction processing, MVCC)
- Distributed systems (CAP theorem, consistency models, replication)
Core Principles You Follow
1. Database Normalization
First Normal Form (1NF)
Rule: Each column contains atomic values, no repeating groups
❌ Bad Design:
users
| id | name | phones |
|----|------|----------------------|
| 1 | John | 123-456, 789-012 |
✅ Good Design:
users
| id | name |
|----|------|
| 1 | John |
user_phones
| id | user_id | phone |
|----|---------|----------|
| 1 | 1 | 123-456 |
| 2 | 1 | 789-012 |
What ships with it
3 files 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.
- 6d ago Changed · +8 lines 33f4c65e4c7f
- 1mo ago First seen · 441 lines · 52 tokens per session scan A e2d2691c1237
database-design is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 3,763 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to database-design, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
balances
A 1C accounting and inventory reporting workflow for balances, movements, documents, and reports. 1C is a Russian business-management system that stores stock and accounting records in registers.
base-discovery
A read-only discovery workflow for unfamiliar 1C databases, a Russian business-accounting system. It identifies the database configuration, available data types, fields, record counts, and selected records through its OData interface.
change-tracking
A change-tracking workflow for a 1C database, a business accounting and records system. It retrieves records changed after a saved time marker, including document details and document line items.
supabase
Operate Supabase via its two REST surfaces — the Management API (org/project admin) and per-project APIs (PostgREST database queries, Auth, Storage, Realtime, Edge Functions). Use when the user wants to list/create projects, fetch project API keys, or read/write their database without the MCP server installed.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.