Borrowing it
Nothing to install: this file belongs to LionelHuanSi/awesome-ai-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LionelHuanSi/awesome-ai-agent-skills/main/.agents/skills/database-design/SKILL.mdgit clone --depth 1 https://github.com/LionelHuanSi/awesome-ai-agent-skillsWrote 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/lionelhuansi/awesome-ai-agent-skills/database-design)<a href="https://agentmods.dev/skills/lionelhuansi/awesome-ai-agent-skills/database-design"><img src="https://agentmods.dev/badge/skills/lionelhuansi/awesome-ai-agent-skills/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/lionelhuansi/awesome-ai-agent-skills/database-design"><img src="https://agentmods.dev/badge/skills/lionelhuansi/awesome-ai-agent-skills/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.00038 | $0.00368 |
| Opus 5 | $0.00019 | $0.00184 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
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 12d 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.
What it actually says
Database Design & Migration Skill
Sourced from PatrickJS/awesome-cursorrules database & ORM rules.
Relational Schema Design Standards
- Primary Keys: Use UUIDv4 or BIGINT (
BIGSERIAL) primary keys. - Foreign Keys & Constraints: Define explicit foreign key constraints with cascade/set null rules.
- Data Types:
- Timestamps: Always use
TIMESTAMPTZ(UTC). - Semi-structured data: Use
JSONBwith GIN indexes instead of raw textJSON. - Financial/Currency values: Use
NUMERIC(12, 2)or integer cents, neverFLOAT.
- Timestamps: Always use
- Audit Fields: Every core table must include
created_at,updated_at, and optionaldeleted_at(for soft deletes).
Indexing & Query Optimization
- Foreign Key Indexing: Always add indexes on foreign key columns.
- Search & Filtering: Create composite indexes for high-frequency multi-column queries.
- N+1 Query Prevention: Enforce eager loading / join fetches to eliminate N+1 database roundtrips.
Migration Best Practices
- Never Modify Live Migrations: Treat existing database migration scripts as immutable.
- Backwards Compatibility: Implement 2-phase non-breaking migrations when renaming or removing columns.
- Tooling: Alembic (Python) / Prisma / Drizzle (TypeScript).
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.
- 12d ago First seen · 32 lines · 38 tokens per session scan A 3b8e871d7be5
database-design is a skill published in the GitHub repository LionelHuanSi/awesome-ai-agent-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 368 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
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
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.
db-repair
Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
analyzing-insights-across-teams
Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard…