databases

databases is a command for Claude Code, Codex from benbjohnson/litestream-skills. It costs 0 tokens per session (600 once invoked), scanned A, original, Apache-2.0.

A command for listing the SQLite databases defined in a Litestream configuration file, along with where each copy is replicated.

In plain words
What is it for?
Use it to inspect database paths and replica types such as S3, Google Cloud Storage, Azure, SFTP, or local files.
Why use it?
It provides a quick check that the expected databases and backup storage destinations are configured.

Command for Claude CodeCodex

Written for Codex and Claude Code: installed under .codex/, but also a Claude Code command (commands/*.md).

Good fit Use it to inspect database paths and replica types such as S3, Google Cloud Storage, Azure, SFTP, or local files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/benbjohnson/litestream-skills/databases
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.

Clone the repo
git clone --depth 1 https://github.com/benbjohnson/litestream-skills

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 databases

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/benbjohnson/litestream-skills/databases"><img src="https://agentmods.dev/badge/commands/benbjohnson/litestream-skills/databases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 600 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00600
Opus 5.5 $0.00000 $0.00240
Sonnet 5.5 $0.00000 $0.00120
Haiku 4.5 $0.00000 $0.00060

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

Security

Grade A, and why

databases 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 2mo 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.

.codex/skills/litestream/commands/databases.md · 135 lines

How it starts

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

databases Command

List all databases in the configuration file.

Synopsis

litestream databases [-config PATH]

Description

The databases command lists all databases defined in your Litestream configuration file along with their replica type.

Flags

Flag Description
-config PATH Configuration file path (default: /etc/litestream.yml)
-no-expand-env Disable environment variable expansion

Output Columns

Column Description
path Path to the SQLite database file
replica Storage backend type (s3, gs, abs, sftp, nats, file, etc.)

Examples

Basic Usage

$ litestream databases

path                    replica
/data/app.db            s3
/data/users.db          s3
/data/logs.db           file

With Custom Config

$ litestream databases -config /etc/litestream-prod.yml

path                    replica
/data/production.db     s3

Use Cases

Verify Configuration

Ensure all expected databases are configured:

$ litestream databases
# Check output includes all your databases

Script Integration

Use in scripts to iterate over databases:

#!/bin/bash
# Check status of all databases
for db in $(litestream databases | tail -n +2 | cut -f1); do
    echo "Checking: $db"
    litestream status "$db"
done

Debugging

Verify configuration is loading correctly:

# With environment expansion
litestream databases

# Without environment expansion
litestream databases -no-expand-env

Configuration Examples

The output reflects your configuration:

dbs:
  - path: /data/app.db
    replica:
      url: s3://bucket/app

  - path: /data/users.db
    replica:
      type: gs
      bucket: my-bucket
      path: users

  - path: /data/logs.db
    replica:
      path: /mnt/backup/logs

Output:

path              replica
/data/app.db      s3
/data/users.db    gs
/data/logs.db     file

Read the full file on GitHub · 135 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. 2mo ago First seen · 135 lines · 0 tokens per session scan A ea86f597e190

Subscribe to this mod's changes

databases is a command published in the GitHub repository benbjohnson/litestream-skills (5 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 600 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-31.

Related

databases compared with commands from other repositories

databases next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
databasesbenbjohnson/litestream-skillsCommand59mo agoApache-2.0A0Claude Code, Codex
initfcakyon/claude-codex-settingsCommand1.2ktodayApache-2.0A0Claude Code
securityajitpratap0/GoSQLXCommand1243d agoApache-2.0A21Claude Code
database-setupimsaif/design-with-claudeCommand112d agoMITA36Claude Code
new-migrationRaNDoM6913/claude-code-superkitCommand3todayMITA22Claude Code
json.batch_getstratalab/strata-coreCommand51mo agoApache-2.0A0Claude Code
json.index.dropstratalab/strata-coreCommand51mo agoApache-2.0A0Claude Code