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/dzianisv/opencode-plugins/opencode-session-dbnpx skills add dzianisv/opencode-plugins --skill opencode-session-dbgit clone --depth 1 https://github.com/dzianisv/opencode-pluginsWhat 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.00096 | $0.02489 |
| Opus 5 | $0.00048 | $0.01244 |
| Sonnet 5 | $0.00019 | $0.00498 |
| Haiku 4.5 | $0.00010 | $0.00249 |
Grade A, and why
opencode-session-db 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 yesterday.
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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Session DB
Read OpenCode sessions and messages directly from SQLite — no running server needed.
Database Location
~/.local/share/opencode/opencode.db # latest/beta channel
~/.local/share/opencode/opencode-{channel}.db # dev, local, etc.
Override: OPENCODE_DB env var. WAL mode is enabled; always open read-only.
Schema Overview
11 tables. The key ones for session reading:
| Table | PK | Key columns |
|---|---|---|
project |
id |
worktree, name |
session |
id |
project_id, title, slug, directory, time_created, time_updated, time_archived |
message |
id |
session_id, time_created, data (JSON: role, tokens, cost, model, error) |
part |
id |
message_id, session_id, time_created, data (JSON: type, text, tool info) |
todo |
(session_id, position) |
content, status, priority |
Message data JSON structure
{"role": "user"|"assistant", "tokens": {...}, "cost": N, "model": {...}, "error": {...}}
Part data JSON structure — discriminated by type
text—{type:"text", text:"..."}tool—{type:"tool", tool:"toolName", input:{...}, output:"...", state:"completed"|"error"|...}reasoning—{type:"reasoning", text:"..."}step-start/step-finish— step boundariessnapshot/patch/compaction— context managementfile— file referencesagent/subtask— delegation
Common Queries
Always open read-only: sqlite3 -readonly "$DB"
# Set DB path
DB=~/.local/share/opencode/opencode.db
List recent sessions
SELECT s.id, s.title, datetime(s.time_created/1000, 'unixepoch') as created,
datetime(s.time_updated/1000, 'unixepoch') as updated, p.name as project
FROM session s JOIN project p ON s.project_id = p.id
WHERE s.time_archived IS NULL
ORDER BY s.time_updated DESC LIMIT 20;
Search sessions by title
SELECT id, title, datetime(s.time_updated/1000, 'unixepoch') as updated
FROM session s WHERE title LIKE '%search term%'
ORDER BY time_updated DESC;
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.
- yesterday First seen · 282 lines · 96 tokens per session scan A 0a29f9d5e0f9
opencode-session-db is a skill published in the GitHub repository dzianisv/opencode-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 2,489 once invoked, about $0.0005 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-31.
Other skills, from other repositories
open-tabletop-gm
You are a seasoned, atmospheric Game Master running a persistent tabletop RPG campaign. Your tone is immersive and descriptive — paint scenes with sensory detail, give NPCs distinct voices, and let choices have real consequences. You lean toward "yes, and..." rulings and fun over rigid rule enforcement, but the world…
hud
Configure HUD display options (layout, presets, display elements).
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
research
Conduct preliminary research on a topic and generate research outline. For academic research, benchmark research, technology selection, etc.
southwest
Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.