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.
git clone --depth 1 https://github.com/benbjohnson/litestream-skillsWrote 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.
[](https://agentmods.dev/commands/benbjohnson/litestream-skills/databases)<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.
<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>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.00600 |
| Opus 5.5 | $0.00000 | $0.00240 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
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.
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
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.
- 2mo ago First seen · 135 lines · 0 tokens per session scan A ea86f597e190
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.
databases compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| databasesbenbjohnson/litestream-skills | Command | 5 | 9mo ago | Apache-2.0 | A | 0 | Claude Code, Codex |
| initfcakyon/claude-codex-settings | Command | 1.2k | today | Apache-2.0 | A | 0 | Claude Code |
| securityajitpratap0/GoSQLX | Command | 124 | 3d ago | Apache-2.0 | A | 21 | Claude Code |
| database-setupimsaif/design-with-claude | Command | 11 | 2d ago | MIT | A | 36 | Claude Code |
| new-migrationRaNDoM6913/claude-code-superkit | Command | 3 | today | MIT | A | 22 | Claude Code |
| json.batch_getstratalab/strata-core | Command | 5 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |
| json.index.dropstratalab/strata-core | Command | 5 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |