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 skills add divinevideo/divine-mobile --skill sqlite-fts5-corruption-rebuildgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/skills/divinevideo/divine-mobile/sqlite-fts5-corruption-rebuild)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/sqlite-fts5-corruption-rebuild"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/sqlite-fts5-corruption-rebuild/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/skills/divinevideo/divine-mobile/sqlite-fts5-corruption-rebuild"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/sqlite-fts5-corruption-rebuild.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00126 | $0.00997 |
| Opus 5.5 | $0.00050 | $0.00399 |
| Sonnet 5.5 | $0.00025 | $0.00199 |
| Haiku 4.5 | $0.00013 | $0.00100 |
Grade A, and why
sqlite-fts5-corruption-rebuild 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 1mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQLite FTS5 Index Corruption from Dirty Data
Problem
SQLite returns "database disk image is malformed" (error code 11) when trying to
UPDATE or INSERT records, even though PRAGMA integrity_check reports the database
as "ok". The error only affects specific records, not all writes.
Context / Trigger Conditions
- Error message:
Error: stepping, database disk image is malformed (11) PRAGMA integrity_checkreturnsok(misleading!)- SELECT queries on the same records work fine
- Only certain records fail to update; other records in the same table update successfully
- The affected records contain text with embedded tabs (
\t), newlines (\n), or other control characters in columns that are indexed by FTS5 - A concurrent process (like a Node.js server) may have the database open
Solution
-
Identify FTS5 tables linked to the affected table:
SELECT name FROM sqlite_master WHERE type='table' AND name LIKE '%fts%'; -
Stop any processes holding the database open (the rebuild requires exclusive access):
kill $(lsof -ti :PORT) # Kill the server process -
Rebuild the FTS5 index:
INSERT INTO table_fts(table_fts) VALUES('rebuild');Replace
table_ftswith your actual FTS5 table name (e.g.,people_fts). -
Retry the failed operation - it should now succeed.
-
Restart your application server.
Verification
- The previously failing UPDATE/INSERT statement now succeeds
- Full-text search queries still return correct results
- No more "malformed" errors on subsequent writes
Example
# Error occurs:
sqlite3 data/tracker.db "UPDATE people SET name = 'More' WHERE id = 11;"
# Error: stepping, database disk image is malformed (11)
# But integrity check passes:
sqlite3 data/tracker.db "PRAGMA integrity_check;"
# ok
# And SELECT works fine:
sqlite3 data/tracker.db "SELECT id, name FROM people WHERE id = 11;"
# 11|More Masajes\t\n\t\tEscort 23 años...
# Fix: Stop server, rebuild FTS5 index
kill $(lsof -ti :3001)
sqlite3 data/tracker.db "INSERT INTO people_fts(people_fts) VALUES('rebuild');"
# Now the update works:
sqlite3 data/tracker.db "UPDATE people SET name = 'More' WHERE id = 11;"
# Success!
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.
- 1mo ago First seen · 104 lines · 126 tokens per session scan A 865f1fc03e03
sqlite-fts5-corruption-rebuild is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 126 tokens to every session and 997 once invoked, about $0.0005 per session on Opus 5.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-09-03.
Other skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.
django-perf-review
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.