A command that shows whether configured SQLite databases are being copied, or replicated, to another location. It reports each database's state, transaction ID, and write-ahead log size.

Use it to check all configured databases or one database, including states such as operational, not initialized, missing, or error.

It helps you find out whether replication is working without inspecting the database files manually.

status — Command for Claude Code and Codex by benbjohnson: A command that shows whether configured SQLite databases are…

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/benbjohnson/litestream-skills/status

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/benbjohnson/litestream-skills/status.svg)](https://agentmods.dev/commands/benbjohnson/litestream-skills/status)

Your own site

<a href="https://agentmods.dev/commands/benbjohnson/litestream-skills/status"><img src="https://agentmods.dev/badge/commands/benbjohnson/litestream-skills/status.svg" alt="Measured on agentmods" 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 786 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00786
Opus 5	$0.00000	$0.00393
Sonnet 5	$0.00000	$0.00157
Haiku 4.5	$0.00000	$0.00079

Measured 5d ago against content hash e6fad1b20e17, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

status scanned grade A with 1 finding 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 5d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl http://localhost:9090/metrics | grep litestream

.codex/skills/litestream/commands/status.md · 138 lines

How it starts

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

status Command

Display replication status for configured databases.

Synopsis

litestream status [-config PATH] [DATABASE_PATH]

Description

The status command shows the current replication state of databases in your configuration file. It displays:

Database path
Current status
Local transaction ID
WAL file size

Flags

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

Output Columns

Column	Description
`database`	Path to the SQLite database file
`status`	Current state: `ok`, `not initialized`, `no database`, `error`
`local txid`	Latest local transaction ID
`wal size`	Current WAL file size

Status Values

Status	Description
`ok`	Database is operational and has been replicated
`not initialized`	Database exists but hasn't been replicated yet
`no database`	Database file doesn't exist at configured path
`error`	Unable to read database status
`unknown`	Status could not be determined

Examples

View All Databases

$ litestream status

database           status            local txid            wal size
/data/app.db       ok                0000000000001234      1.2 MB
/data/users.db     ok                0000000000000567      256 KB
/data/logs.db      not initialized   -                     0 B

View Specific Database

$ litestream status /data/app.db

database           status            local txid            wal size
/data/app.db       ok                0000000000001234      1.2 MB

With Custom Config

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

Understanding the Output

Transaction ID (TXID)

The local TXID shows the latest transaction that has been:

Written to the WAL
Converted to LTX format
Stored locally

Read the full file on GitHub · 138 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.

5d ago First seen · 138 lines · 0 tokens per session scan A e6fad1b20e17

Subscribe to this mod's changes

status is a command published in the GitHub repository benbjohnson/litestream-skills (5 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 786 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Databases

status