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.
npx agentmods add skills/sonichi/sutando/db-browsernpx skills add sonichi/sutando --skill db-browsergit clone --depth 1 https://github.com/sonichi/sutandoWhat 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 | $0.00027 | $0.00634 |
| Opus 5 | $0.00014 | $0.00317 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
db-browser 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 3d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Browser
Install DB Browser for SQLite via Homebrew if it isn't already installed, then open a given .sqlite file in it. Macos only — uses brew --cask + open -a.
Usage: /db-browser <path-to.sqlite>
ARGUMENTS: $ARGUMENTS
Steps
- Resolve the path argument. If empty, default to
$(bash scripts/sutando-config.sh workspace)/data/conversation.sqlite(the M0 helper — readssutando.config.local.json, defaulting to<repo>/workspace/data/conversation.sqlite;$SUTANDO_WORKSPACEno longer honored as of v0.8 / #1440). Bail with an error if the file doesn't exist. - Check whether DB Browser for SQLite is installed:
mdfind "kMDItemKind == 'Application'" 2>/dev/null | grep -qi 'DB Browser for SQLite'(or[ -d /Applications/DB\ Browser\ for\ SQLite.app ]). If installed, skip step 3. - Install via Homebrew:
brew install --cask db-browser-for-sqlite. Requires brew. If brew is missing, stop and ask the user to install brew first. - If DB Browser is already running on a DIFFERENT db file (its cached snapshot of THAT db won't auto-refresh when you switch files), quit it first:
osascript -e 'tell application "DB Browser for SQLite" to quit'; sleep 2. Skip if not running. - Open the file:
open -a "DB Browser for SQLite" "<resolved-path>". Sleep ~2s so the window is up before reporting back. - Confirm: print the resolved path + verify DB Browser has the file open via
lsof -c "DB Browser" 2>/dev/null | grep "<resolved-path>".
Notes
- DB Browser caches the schema + first page of data at open time. If the on-disk db file changes underneath (e.g. a migration drops tables, a writer adds rows), the open DB Browser window keeps showing the stale view until you re-open it. That's why step 4 quits first when re-opening — same-file re-open is also a valid refresh trigger.
- WAL flush: if the db is in WAL mode and recent writes haven't merged into the main file, the
.sqlite-walsidecar holds them. DB Browser reads both — no checkpoint needed. (Runsqlite3 <db> 'PRAGMA wal_checkpoint(TRUNCATE);'only if you want a single-file dump.) - This skill does NOT screenshot, query, or modify the db. Just install + open. Anything else (screenshot for a PR, run a SQL via Execute SQL, export CSV) is the operator's job in the GUI.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 29 lines · 27 tokens per session scan A 492e11f24d4a
db-browser is a skill published in the GitHub repository sonichi/sutando (389 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 634 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.
Other skills, from other repositories
vellum-migration-checklist
Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.
sqlite-schema-design
Design or review schemas for crates/cloudsync using SQLite Sync constraints, not generic SQLite advice. Use when adding synced tables, changing synced columns, or planning CloudSync-safe migrations.
reactive-sqlite-ui
Build SQLite-backed reactive UI in apps/desktop using stable patterns for reads, selection, forms, writes, and loading states. Use when implementing or reviewing screens built on useDrizzleLiveQuery and SQLite mutations.
query-performance
Validate what a ClickHouse query actually costs before merging it — at production scale through read-only environment access, or on a revived Testcontainers dataset extrapolated to 20k/500k/1M entities. Use when a DAO query changes, when an endpoint is slow, or when a reviewer asks "what does this cost at scale".
migrate-to-sqlite
Migrate a TinyBase table to SQLite. Use when asked to move a data domain (e.g. templates, vocabs) from the TinyBase store to the app SQLite database.
contacts
Manage contacts, communication channels, access control, and invite links.