netlify-database-cli-commands

A reference for Netlify CLI commands that manage Netlify Database, a hosted database service, from a terminal. The commands can initialize the database, inspect migrations, connect to it, and perform related setup.

In plain words
What is it for?
Use it to initialize a database, check its status, connect to it, inspect credentials, and manage database migrations from the Netlify CLI.
Why use it?
It gives the exact command forms and options needed to inspect or script database work, including machine-readable output for agents.

Cursor rule

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 rules/netlify/context-and-tools/netlify-database-cli-commands
Clone the repo
git clone --depth 1 https://github.com/netlify/context-and-tools
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 919 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.00018 $0.00919
Opus 5 $0.00009 $0.00460
Sonnet 5 $0.00004 $0.00184
Haiku 4.5 $0.00002 $0.00092

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

Security

Grade A, and why

netlify-database-cli-commands 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.

cursor/rules/netlify-database-cli-commands.mdc · 91 lines

How it starts

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

Netlify CLI commands for Netlify Database

The CLI ships a complete database surface under netlify database (alias: netlify db). Requires CLI 26.0.0+. Most commands accept --json for machine-readable output — useful when scripting or reading results from an agent.

netlify database init

Interactive bootstrap: installs @netlify/database (and Drizzle if chosen), writes drizzle.config.ts, scaffolds and applies a starter migration, and runs a sample query. Use --yes for non-interactive mode.

netlify database status

Reports whether the database is enabled, whether @netlify/database is installed, the connection string for the active branch, and the applied/pending/missing/out-of-order migrations. Defaults to the local development database — pass --branch <name> to target a remote preview or production branch.

netlify database status                          # local
netlify database status --branch my-feature      # remote branch
netlify database status --json
netlify database status --show-credentials       # include username/password in connection string

netlify database connect

Connects to the database. Defaults to an interactive REPL — for agent and script use, always pass --query for one-shot execution:

# List tables
netlify database connect --query "SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'"

# Inspect columns
netlify database connect --query "SELECT column_name, data_type, is_nullable FROM information_schema.columns WHERE table_name = 'items'"

# JSON output
netlify database connect --query "SELECT * FROM items LIMIT 10" --json

# Get connection details only (no query)
netlify database connect --json

Never run DDL (CREATE, ALTER, DROP, TRUNCATE) through netlify database connect, psql, or any other direct connection. Schema changes go through migration files — out-of-band DDL drifts the migration history from the actual schema.

netlify database migrations new

Read the full file on GitHub · 91 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 · 91 lines · 18 tokens per session scan A 51ba8156c46d

Subscribe to this mod's changes

netlify-database-cli-commands is a cursor rule published in the GitHub repository netlify/context-and-tools (36 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 919 once invoked, about $0.0001 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.