vnx-orchestration: Skill for Claude Code

.claude/skills/database-engineer/SKILL.md

database-engineer is a skill for Claude Code from Vinix24/vnx-orchestration. It costs 0 tokens per session (3,712 once invoked), scanned A, original, MIT.

A specialist guide for SQLite, a small database often used inside applications. It focuses on safely changing database structure, moving data, keeping separate customers or projects isolated, and using SQLite’s full-text search.

In plain words
What is it for?
Use it when writing or reviewing SQLite migrations, schema changes, imports, data comparisons, unique keys, full-text search rebuilds, or transaction rollback logic. It is also for investigating migrations that finish with wrong counts or run unusually slowly.
Why use it?
It helps prevent migrations—changes that update a database’s structure or data—from silently losing rows, mixing tenant data, or producing incorrect results. It also highlights common problems with conflict-handling statements and slow table comparisons.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Codex.

This is Vinix24/vnx-orchestration's own configuration. It tells Claude Code how to work on vnx-orchestration itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vnx-orchestration configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/database-engineer/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Vinix24/vnx-orchestration

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.

agentmods badge for database-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/database-engineer/github.svg)](https://agentmods.dev/skills/vinix24/vnx-orchestration/database-engineer)
Your own site
<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/database-engineer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/database-engineer/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.

agentmods 80×15 button for database-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/database-engineer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/database-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,712 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00000 $0.03712
Opus 5.5 $0.00000 $0.01485
Sonnet 5.5 $0.00000 $0.00742
Haiku 4.5 $0.00000 $0.00371

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

Security

Grade A, and why

database-engineer 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 1mo 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.

.claude/skills/database-engineer/SKILL.md · 198 lines

How it starts

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

Database Engineer

SQLite-domain specialist for migrations and data integrity.

Core Mission

Migrations are integration code. Most "data" bugs aren't algorithmic — they're contract bugs between schema, importer, and verifier. This skill exists because P4 (the VNX one-shot consolidation migrator) consumed 5 fix-forward rounds before converging, and the bugs were almost entirely SQLite/multi-tenant gotchas a generalist would miss.

The specific recurring failure-modes are catalogued in references/bug-taxonomy.md with concrete VNX examples. Read it before writing any migration code.

When to Use

  • Writing or editing files under schemas/migrations/
  • Touching _import_table, _compare_counts, or any code that ATTACHes / SELECTs / INSERTs across tenant boundaries
  • Designing UNIQUE constraints or primary keys for any table that will hold multi-project rows
  • Adding JOIN or correlated-subquery code that scans tables ≥10k rows
  • Debugging a migration that "completed" but produced wrong row counts
  • Operator complains "stuck at 100% CPU for hours" — likely O(N×M) (see references/sqlite-fts5-gotchas.md)
  • Any code that calls INSERT OR IGNORE or INSERT OR REPLACE

STEP 0 — Foundational Check (Mandatory)

BEFORE proposing any design, fix, or implementation:

  1. Consult relevant ADRs in docs/governance/decisions/. Special attention to:

    • ADR-005 (NDJSON audit ledger as primary observability)
    • ADR-007 (multi-tenant project_id stamping; composite keys for central state DBs)
    • ADR-010 (subprocess adapter as canonical Claude routing) List any ADR that applies to the task and how it constrains your solution.
  2. Consult relevant memory in ~/.claude/projects/-Users-vincentvandeth-Development-vnx-dev-githost/memory/MEMORY.md — particularly entries about past architectural incidents.

  3. Check P4-style incident docs in claudedocs/ for analogous failures (e.g., 2026-05-09-p4-migration-architecture-lessons.md for multi-tenant migration patterns).

Read the full file on GitHub · 198 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. 1mo ago First seen · 198 lines · 0 tokens per session scan A 97584fcaa5b6

Subscribe to this mod's changes

database-engineer is a skill published in the GitHub repository Vinix24/vnx-orchestration (62 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,712 tokens. 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.