A command for listing LTX files, which are Litestream's backup files containing SQLite database changes.

Use it to inspect available backup and restore points for a configured database or replica URL.

It shows which backup files exist, their transaction ranges, sizes, and creation times, making it easier to check backups and investigate replication problems.

ltx — Command for Claude Code and Codex by benbjohnson

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.

README.md

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

Your own site

<a href="https://agentmods.dev/commands/benbjohnson/litestream-skills/ltx"><img src="https://agentmods.dev/badge/commands/benbjohnson/litestream-skills/ltx.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 989 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00989
Opus 5	$0.00000	$0.00495
Sonnet 5	$0.00000	$0.00198
Haiku 4.5	$0.00000	$0.00099

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

Security

Grade A, and why

ltx 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 8d 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/ltx.md · 166 lines

How it starts

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

ltx Command

List LTX files available for a database.

Synopsis

# From configured database
litestream ltx [-config PATH] DB_PATH

# From replica URL
litestream ltx REPLICA_URL

Description

The ltx command lists all LTX (Log Transaction) files available for a database. This is useful for:

Verifying backups exist
Finding available restore points
Debugging replication issues
Understanding the backup timeline

Flags

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

Output Columns

Column	Description
`min_txid`	Starting transaction ID
`max_txid`	Ending transaction ID
`size`	File size in bytes
`created`	Creation timestamp (RFC3339)

Examples

List from Config

$ litestream ltx /data/app.db

min_txid              max_txid              size     created
0000000000000001      0000000000000100      4096     2024-01-15T10:00:00Z
0000000000000101      0000000000000200      8192     2024-01-15T10:30:00Z
0000000000000201      0000000000000300      4096     2024-01-15T11:00:00Z

List from Replica URL

$ litestream ltx s3://mybucket/app-backup

min_txid              max_txid              size     created
0000000000000001      0000000000001000      102400   2024-01-15T00:00:00Z

Check Specific Storage

# S3
litestream ltx s3://bucket/path

# GCS
litestream ltx gs://bucket/path

# Azure
litestream ltx abs://container@account/path

# SFTP
litestream ltx sftp://user@host/path

Understanding Output

Transaction ID Range

Each LTX file covers a range of transactions:

min_txid: First transaction in file
max_txid: Last transaction in file

Files should be contiguous for complete recovery.

Compaction Levels

LTX files exist at different compaction levels:

L0: Raw files from WAL changes (many small files)
L1+: Compacted files (fewer, larger files)

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

8d ago First seen · 166 lines · 0 tokens per session scan A ed525435dd97

Subscribe to this mod's changes

ltx 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 989 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.

Databases

ltx