A database-schema naming audit. A database schema is the structure that defines tables, columns, relationships, and their names.

Use it to check table and column casing, singular or plural names, foreign-key and Boolean names, timestamps, reserved words, and vague identifiers.

Consistent names make relationships easier to understand and reduce bugs caused by mixed casing, reserved SQL words, unclear columns, or unpredictable foreign-key names.

db-naming — Skill for Claude Code by Hainrixz

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.

Any agent

npx skills add Hainrixz/claude-db --skill db-naming

Clone the repo

git clone --depth 1 https://github.com/Hainrixz/claude-db

Made for: Claude Code.

Or install claude-db, the plugin that ships this one along with the rest of its 36 skills, 6 agents, 1 hook.

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/skills/hainrixz/claude-db/db-naming/github.svg)](https://agentmods.dev/skills/hainrixz/claude-db/db-naming)

Your own site

<a href="https://agentmods.dev/skills/hainrixz/claude-db/db-naming"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-db/db-naming/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/skills/hainrixz/claude-db/db-naming"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-db/db-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 904 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.00065	$0.00904
Opus 5	$0.00032	$0.00452
Sonnet 5	$0.00013	$0.00181
Haiku 4.5	$0.00006	$0.00090

Measured 9d ago against content hash 1be43cc96f63, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

db-naming 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 9d 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.

skills/db-naming/SKILL.md · 48 lines

How it starts

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

db-naming (M7)

Naming is the schema's documentation: consistent, predictable identifiers make joins obvious and reduce the quoting/casing bugs that creep in across ORMs and engines. It is low-weight (Naming category, design axis) — real but never the headline. This module is design-axis and never caps.

What it checks

Casing / pluralization consistency: a mix of snake_case and camelCase, or singular and plural table names (user, orders, OrderItem) in one schema — pick one and hold it.
Reserved words & case-folding traps: identifiers that are SQL reserved words (user, order, group, select) or that rely on case ("User" quoted) — Postgres folds unquoted to lowercase, MySQL is filesystem/case-config dependent; mixed quoting causes "relation does not exist" bugs.
FK naming: FK columns not following a predictable <referenced>_id pattern, so joins aren't self-evident.
Boolean naming: booleans not prefixed is_/has_/can_, or negative names (not_active) that invert logic.
Opaque / ambiguous names: data, info, value, flag, temp, col1, abbreviations without a glossary, or timestamps not suffixed _at.

Axis & severity

Axis: design; magnitude almost always low, banded honestly.
Reserved-word unquoted identifier that breaks across engines: severity 2–3, warn.
Schema-wide casing/pluralization inconsistency: severity 2, warn, fixable: proposed (rename is high-blast-radius — never auto).
Opaque column name / missing _at suffix: severity 1, warn.
M7 never caps any score; it is the smallest-weight design category.

Tier-0 static check

Parse DDL/snapshot via scripts/parse-schema.mjs: tally identifier casing styles and table pluralization; match identifiers against a reserved-word list per engine; check FK columns against the <table>_id pattern; flag boolean columns without is_/has_/can_ and opaque names. This is fully static and directional.

Tier-1 verification query

Confirm live identifier inventory and quoting:

-- $DATABASE_URL, read-only
SELECT table_name, column_name FROM information_schema.columns
WHERE table_schema NOT IN ('pg_catalog','information_schema')
ORDER BY table_name;   -- inspect casing/plurality/reserved words across the real catalog

Read the full file on GitHub · 48 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.

9d ago First seen · 48 lines · 65 tokens per session scan A 1be43cc96f63

Subscribe to this mod's changes

db-naming is a skill published in the GitHub repository Hainrixz/claude-db (19 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 904 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-30.

Claude Code Databases ai claude data-modeling database-migrations

dynamodb

Use when modeling or operating a DynamoDB table: deriving partition/sort keys from access patterns, single-table vs table-per-entity, adding a GSI/LSI, on-demand vs provisioned capacity, or diagnosing hot-partition throttling. NOT relational schema/SQL/EXPLAIN (that is postgresdb), NOT aggregation-pipeline document…

ericrisco/rsc-harness · 82 tokens

malloy-lookml-review

Analyze LookML files as prior art for Malloy modeling. Used during Step 1 (DISCOVER) when .lkml files are present. Coordinates reference files that extract business logic, relationships, and curation decisions. Works with or without a database connection.

malloydata/publisher · 58 tokens

db-naming