add-database-driver

A command that scaffolds and connects a new database or data-warehouse driver throughout Altimate Code, including its registry, discovery, tests, and documentation.

In plain words
What is it for?
Use it when adding support for a database such as CockroachDB, TimescaleDB, Cassandra, or Neo4j, after checking its client, versions, authentication, SQL behavior, Docker image, and dbt adapter.
Why use it?
It removes the risk of adding a driver in one place while missing one of the many other places the application must know about it.

Command for Claude Code

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 commands/altimateai/altimate-code/add-database-driver
Clone the repo
git clone --depth 1 https://github.com/AltimateAI/altimate-code

Made for: Claude Code.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,697 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 $0.00046 $0.01697
Opus 5 $0.00023 $0.00848
Sonnet 5 $0.00009 $0.00339
Haiku 4.5 $0.00005 $0.00170

Measured 2d ago against content hash ddd89039a713, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-database-driver 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 2d 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/commands/add-database-driver.md · 182 lines

How it starts

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

Add Database Driver

Scaffold and fully integrate a new database/warehouse driver into Altimate Code. This command handles all 23 integration points — driver code, registry, discovery, finops, tests, and documentation.

Input

$ARGUMENTS = the database name (e.g., cockroachdb, timescaledb, cassandra, neo4j).

If empty, ask: "Which database should I add support for?"

Step 0: Research

Before writing any code, research the database:

  1. Find the official Node.js/TypeScript client package on npm. Search for @{database}/client, {database}-js, or similar.
  2. Check supported server versions — which versions are not EOL?
  3. Identify auth methods — password, token, TLS/certificate, connection string, cloud-specific?
  4. Check SQL dialect — standard SQL? Custom syntax? LIMIT vs TOP vs FETCH FIRST? System tables for schemas/tables/columns?
  5. Find Docker image — official image on Docker Hub for E2E testing?
  6. Check if dbt adapter exists — search for dbt-{database} on PyPI.

Present findings to the user before proceeding:

## Research: {Database}

- **npm package**: `{package}` (v{version})
- **Server versions**: {non-EOL versions}
- **Auth methods**: {list}
- **SQL dialect**: {notes on LIMIT, system tables, parameterized queries}
- **Docker image**: `{image}:{tag}`
- **dbt adapter**: {exists/not found}

Proceed with implementation?

Step 1: Read Reference Document

Read the comprehensive checklist:

cat packages/drivers/ADDING_A_DRIVER.md

This document has all 23 integration points with exact file paths and code patterns.

Step 2: Read Existing Driver for Pattern

Read a similar existing driver as a template. Choose based on database type:

  • SQL database with password auth → read packages/drivers/src/mysql.ts
  • Cloud warehouse with token auth → read packages/drivers/src/databricks.ts
  • Database with connection string support → read packages/drivers/src/postgres.ts
  • HTTP-based client → read packages/drivers/src/clickhouse.ts
  • Document database (non-SQL) → read packages/drivers/src/mongodb.ts

Read the full file on GitHub · 182 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. 2d ago First seen · 182 lines · 46 tokens per session scan A ddd89039a713

Subscribe to this mod's changes

add-database-driver is a command published in the GitHub repository AltimateAI/altimate-code (803 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,697 once invoked, about $0.0002 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.