database-verification

database-verification is a skill for Claude Code, Codex from vladkesler/initrunner. It costs 29 tokens per session (905 once invoked), scanned A, original, Apache-2.0.

A shell-based skill for checking whether a database is reachable, has the expected tables or collections, and satisfies data-integrity rules.

In plain words
What is it for?
It is for verifying PostgreSQL, Redis, SQLite, MySQL or MariaDB, and MongoDB connectivity, schemas, migrations, and integrity constraints.
Why use it?
It helps distinguish database connection problems from schema or data problems when tests or migrations fail.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for verifying PostgreSQL, Redis, SQLite, MySQL or MariaDB, and MongoDB connectivity, schemas, migrations, and integrity constraints.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vladkesler/initrunner/database-verification
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 vladkesler/initrunner --skill database-verification
Clone the repo
git clone --depth 1 https://github.com/vladkesler/initrunner

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-verification

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/vladkesler/initrunner/database-verification"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/database-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 905 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.00029 $0.00905
Opus 5.5 $0.00012 $0.00362
Sonnet 5.5 $0.00006 $0.00181
Haiku 4.5 $0.00003 $0.00090

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

Security

Grade A, and why

database-verification 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.

examples/roles/integration-tester/skills/database-verification/SKILL.md · 140 lines

How it starts

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

Database verification skill using standard database CLI tools.

When to activate

Use this skill when tests fail with connection errors or timeouts to a database, when database-related tests exist in the test suite, when docker-compose or similar configs define database services, or when a migration has recently been applied and needs verification.

Connectivity checks

Test reachability before running any data queries. Each database has its own tool:

PostgreSQL

pg_isready -h host -p 5432

Returns exit code 0 if accepting connections. For authenticated check:

psql -h host -p 5432 -U user -d dbname -c "SELECT 1"

Redis

redis-cli -h host -p 6379 ping

Expected response: PONG.

SQLite

sqlite3 /path/to/file.db ".tables"

Returns the list of tables. A missing file or corrupt database produces an error.

MySQL / MariaDB

mysql -h host -u user -p -e "SELECT 1"

Or check just connectivity:

mysqladmin -h host -u user ping

MongoDB

mongosh --host host --port 27017 --eval "db.runCommand({ ping: 1 })"

Schema verification

After connectivity is confirmed:

  1. Tables exist -- query the information schema or equivalent to list tables; compare against expected table names.
  2. Columns match -- for each critical table, list columns and types; verify expected columns are present with correct types.
  3. Indexes present -- check that performance-critical indexes exist (primary keys, foreign key indexes, unique constraints).
  4. Constraints -- verify NOT NULL, UNIQUE, and foreign key constraints are in place on the relevant columns.

Data integrity

  • Row counts -- check that tables have expected minimum rows (not empty when they should be populated).
  • Foreign key consistency -- verify that foreign key references point to existing rows (no orphaned records).
  • Null checks -- scan NOT NULL columns for unexpected nulls (can happen if constraints were added after data).
  • Duplicate detection -- check unique columns for duplicates when constraints might be missing.

Read the full file on GitHub · 140 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 · 140 lines · 29 tokens per session scan A 3e1545f3bb2b

Subscribe to this mod's changes

database-verification is a skill published in the GitHub repository vladkesler/initrunner (41 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 905 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-08-30.