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/ssube/conclave/sqlitenpx skills add ssube/conclave --skill sqlitegit clone --depth 1 https://github.com/ssube/conclaveWhat 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.00034 | $0.00410 |
| Opus 5 | $0.00017 | $0.00205 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
sqlite 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 Query Skill
Execute SQL queries against a SQLite database with formatted output.
Usage
Execute a query
bash {baseDir}/query.sh query "SELECT * FROM items LIMIT 5" [--format table|json|csv]
Output formats:
table(default): Formatted table with headersjson: JSON array of objectscsv: CSV with header row
List all tables
bash {baseDir}/query.sh tables
Describe table schema
bash {baseDir}/query.sh schema <table>
Environment Variables
SQLITE_DB_PATH: Path to the SQLite database file (required)
Security
- Only SELECT queries are allowed via the
querycommand - INSERT, UPDATE, DELETE, DROP, CREATE, ALTER are rejected
- Queries are validated before execution
Examples
# Inspect the database
bash {baseDir}/query.sh tables
bash {baseDir}/query.sh schema items
# Query with different formats
bash {baseDir}/query.sh query "SELECT name, status FROM items ORDER BY name" --format table
bash {baseDir}/query.sh query "SELECT * FROM logs WHERE date > '2025-01-01'" --format json
bash {baseDir}/query.sh query "SELECT * FROM metrics" --format csv > export.csv
Troubleshooting
"no such table" error
Run bash {baseDir}/query.sh tables to list available tables.
Database locked
Another process is writing. SQLite handles this automatically — wait and retry.
Database not found
Check that SQLITE_DB_PATH is set to a valid file path.
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 · 71 lines · 34 tokens per session scan A 278c1cc1ceee
sqlite is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 410 once invoked, about $0.0002 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
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
mempalace-recall
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall…
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.