database-schema-designer

database-schema-designer is a skill for Claude Code, Codex from OneWave-AI/ClaudeCodeUnleashed. It costs 54 tokens per session (1,811 once invoked), scanned A, original, MIT.

Een hulpmiddel voor het ontwerpen van de structuur van SQL- en NoSQL-databases. Het beschrijft tabellen of documenten, verbanden, zoekindexen en beperkingen, en kan ERD-diagrammen en migratiescripts maken.

In plain words
What is it for?
Voor het plannen van een databasestructuur, het kiezen van relaties en indexen, het voorbereiden van databasemigraties en het afwegen van SQL- en NoSQL-modellen.
Why use it?
Het voorkomt dat gegevens onnodig dubbel worden opgeslagen of dat veelgebruikte zoekopdrachten traag worden. Het maakt ook belangrijke ontwerpkeuzes vooraf zichtbaar.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/onewave-ai/claudecodeunleashed/database-schema-designer
Any agent
npx skills add OneWave-AI/ClaudeCodeUnleashed --skill database-schema-designer
Clone the repo
git clone --depth 1 https://github.com/OneWave-AI/ClaudeCodeUnleashed

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for database-schema-designer

README.md
[![agentmods](https://agentmods.dev/badge/skills/onewave-ai/claudecodeunleashed/database-schema-designer.svg)](https://agentmods.dev/skills/onewave-ai/claudecodeunleashed/database-schema-designer)
Your own site
<a href="https://agentmods.dev/skills/onewave-ai/claudecodeunleashed/database-schema-designer"><img src="https://agentmods.dev/badge/skills/onewave-ai/claudecodeunleashed/database-schema-designer.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,811 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.01811
Opus 5 $0.00027 $0.00905
Sonnet 5 $0.00011 $0.00362
Haiku 4.5 $0.00005 $0.00181

Measured 5d ago against content hash 28fa66f474b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

database-schema-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 5d 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.

assets/starter-skills/database-schema-designer/SKILL.md · 278 lines

How it starts

The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Database Schema Designer

Design optimized, scalable database schemas with proper relationships and indexes.

Instructions

When a user needs database schema design:

  1. Gather Requirements:

    • What type of database (PostgreSQL, MySQL, MongoDB, etc.)?
    • What is the application domain?
    • What are the main entities/resources?
    • What queries will be most common?
    • Expected data volume and growth?
    • Performance requirements?
    • Specific constraints or compliance needs?
  2. Design Schema Following Best Practices:

    For SQL Databases:

    • Identify entities and their attributes
    • Define primary keys (prefer UUIDs for distributed systems)
    • Establish relationships (1:1, 1:N, N:M)
    • Normalize to 3NF (unless denormalization needed for performance)
    • Add appropriate indexes
    • Define foreign key constraints
    • Include timestamps (created_at, updated_at)
    • Add soft delete flags if needed
    • Plan for data archival

    For NoSQL Databases:

    • Design for access patterns (query-first approach)
    • Embed vs reference decision
    • Plan for denormalization
    • Design indexes for common queries
    • Consider document size limits
    • Plan for eventual consistency
  3. Generate Complete Schema:

    SQL Schema Output:

    -- [Entity Name] Table
    -- Purpose: [Description]
    
    CREATE TABLE [table_name] (
      id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
      [field_name] [TYPE] [CONSTRAINTS],
      created_at TIMESTAMP NOT NULL DEFAULT NOW(),
      updated_at TIMESTAMP NOT NULL DEFAULT NOW(),
      deleted_at TIMESTAMP
    );
    
    -- Indexes
    CREATE INDEX idx_[table]_[field] ON [table]([field]);
    CREATE INDEX idx_[table]_[field1]_[field2] ON [table]([field1], [field2]);
    
    -- Foreign Keys
    ALTER TABLE [child_table]
      ADD CONSTRAINT fk_[constraint_name]
      FOREIGN KEY ([foreign_key_field])
      REFERENCES [parent_table](id)
      ON DELETE CASCADE;
    

    NoSQL Schema Output (MongoDB example):

    // [Collection Name]
    // Purpose: [Description]
    
    {
      _id: ObjectId,
      [field_name]: [type],
    
      // Embedded document
      [embedded_object]: {
        field1: type,
        field2: type
      },
    
      // Reference
      [related_id]: ObjectId,  // Ref to [other_collection]
    
      created_at: ISODate,
      updated_at: ISODate
    }
    
    // Indexes
    db.[collection].createIndex({ field: 1 })
    db.[collection].createIndex({ field1: 1, field2: -1 })
    db.[collection].createIndex({ field: "text" })  // Text search
    

Read the full file on GitHub · 278 lines

Changes

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.

  1. 5d ago First seen · 278 lines · 54 tokens per session scan A 28fa66f474b8

Subscribe to this mod's changes

database-schema-designer is a skill published in the GitHub repository OneWave-AI/ClaudeCodeUnleashed (5 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 1,811 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.

Related

Other skills, from other repositories

schema-exploration

Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.

langchain-ai/deepagents · 57 tokens

debugging

How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.

tursodatabase/turso · 28 tokens

sdk-design

Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…

gridaco/grida · 199 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

supabase

Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…

PentesterFlow/agent · 120 tokens

nornicdb-cypher-queries

Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.

orneryd/NornicDB · 79 tokens