What is design-data-model?

A database schema plan based on how data will be read and changed, including relationships, uniqueness rules, constraints, and indexes.

Use it to define entities and columns, nullability, keys, relationships, database-enforced rules, useful indexes, and deliberate denormalisation.

It helps keep data correct in the database and avoids slow queries or speculative indexes that add maintenance cost.

design-data-model — Command for Claude Code by Amey-Thakur/AI-SKILLS

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.

Clone the repo

git clone --depth 1 https://github.com/Amey-Thakur/AI-SKILLS

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/amey-thakur/ai-skills/design-data-model/github.svg)](https://agentmods.dev/commands/amey-thakur/ai-skills/design-data-model)

Your own site

<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/design-data-model"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/design-data-model/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/design-data-model"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/design-data-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 235 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00235
Opus 5.5	$0.00008	$0.00094
Sonnet 5.5	$0.00004	$0.00047
Haiku 4.5	$0.00002	$0.00023

Measured 2mo ago against content hash d56947d6bd20, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-data-model 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 2mo 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.

commands/design-data-model.md · 36 lines

What it actually says

You were invoked as a slash command. The user's input:

$ARGUMENTS

Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.

Design a data model for:

{domain}

Access patterns: {access}

Use schema-design, database-normalization, and indexing-strategy.

Produce:

Entities, attributes, and relationships with cardinality.
Keys, and what makes each row unique.
Constraints that enforce the invariants in the database rather than in application code.
Indexes derived from the stated access patterns.
Where you would denormalise and what that costs.
What this model makes hard, so the trade is visible.

Rules: enforce invariants in the schema where the database can. State the nullability of every column deliberately. Do not add indexes speculatively. Name what future requirement would force a restructure.

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.

2mo ago First seen · 36 lines · 19 tokens per session scan A d56947d6bd20

Subscribe to this mod's changes

design-data-model is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (13 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 235 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Claude Code Databases agent-skills ai-agents ai-skills claude-skills cursor

design-data-model next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
design-data-modelAmey-Thakur/AI-SKILLS	Command	13	2mo ago	MIT	A	19	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code