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/vikasudasi/skill-vault/sqlite-optimizationnpx skills add vikasudasi/skill-vault --skill sqlite-optimizationgit clone --depth 1 https://github.com/vikasudasi/skill-vaultWhat 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.00026 | $0.00445 |
| Opus 5 | $0.00013 | $0.00222 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
sqlite-optimization 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.
What it actually says
SQLite Optimization for Application Use
Use when your SQLite-backed app is slow, hitting lock errors, or you're scaling a single-file database for concurrent readers.
Connection setup (do this every time)
PRAGMA journal_mode=WAL;
PRAGMA foreign_keys=ON;
PRAGMA synchronous=NORMAL;
WAL lets readers run concurrently with a single writer; synchronous=NORMAL is
safe with WAL and much faster than FULL.
Indexes
- Index foreign keys and columns used in
WHERE/JOIN/ORDER BY. - A composite index
(a, b)servesWHERE a=?ANDWHERE a=? AND b=?, notWHERE b=?. - Confirm with
EXPLAIN QUERY PLAN.
Concurrency-safe writes
One shared connection with check_same_thread=False needs a single lock
around any multi-statement transaction — serialize writes through one
threading.RLock (see Skill Vault's db_lock). Interleaved statements on one
connection raise cannot start a transaction within a transaction.
Profiling
EXPLAIN QUERY PLAN SELECT ...
.timer on
Read the plan left-to-right; a SCAN on a big table usually means a missing index.
Pitfalls
PRAGMA journal_mode=WALsurvives per connection, but must be set on the connection that does the work — set it once at connect.- Don't open a new connection per query in a loop; reuse one and lock writes.
- Back up with
sqlite3 .backuporconn.backup()(WAL safe), never by copying the file alone.
What ships with it
2 files 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 · 57 lines · 26 tokens per session scan A d87afb70a02f
sqlite-optimization is a skill published in the GitHub repository vikasudasi/skill-vault (0 stars, last pushed 16d ago), licensed Apache-2.0. It adds 26 tokens to every session and 445 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-31.
Other skills, from other repositories
sql-query-optimization
Diagnoses and optimises slow SQL queries using EXPLAIN ANALYZE. Covers identifying bottlenecks (sequential scans, bad estimates, heap fetches), index strategy, query rewrites, and verification. Invoked when the user asks to optimize a query, fix a slow database query, or improve database performance.
sql-optimization
SQL query optimization techniques and best practices.
SQL Query Optimizer
Reviews SQL queries for performance issues and rewrites them with optimized execution plans.
sql-agent
Write, optimize, and explain SQL queries. Use when user needs to write a query, debug slow SQL, understand a query plan, or design a schema.
sql-sentinel
Audit SQL for the cost & performance anti-patterns that burn warehouse credits. Catches SELECT , full-table scans, non-sargable predicates, Cartesian joins, NULL-trap NOT IN, and 17 more rules. Scores warehouse health 0-100 and outputs a prioritized cost-reduction plan for BigQuery, Snowflake, Redshift, and Postgres.
postgresql-expert
Expert-level PostgreSQL database administration, advanced queries, performance tuning, and production operations.