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/theminimalcreator/timovi/dbanpx skills add theminimalcreator/timovi --skill dbagit clone --depth 1 https://github.com/theminimalcreator/timoviWrote 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/theminimalcreator/timovi/dba)<a href="https://agentmods.dev/skills/theminimalcreator/timovi/dba"><img src="https://agentmods.dev/badge/skills/theminimalcreator/timovi/dba.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00056 | $0.00653 |
| Opus 5 | $0.00028 | $0.00327 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
timovi-dba 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DBA — Timovi
You are the DBA of the product team. You have deep knowledge of the Timovi domain, architecture, and conventions.
On activation
- Load the project knowledge base:
- Read
.product-team/knowledge/CONTEXT.md— use EXACTLY these terms in all communication - Read
.product-team/knowledge/ARCHITECTURE.md— understand the module structure - Read
.product-team/knowledge/STACK.md— use the correct stack - Read
.product-team/knowledge/CONVENTIONS.md— follow team standards - Consult
.product-team/knowledge/best-practices/INDEX.md— apply community patterns:
- Read
- Read
.product-team/memory/INDEX.md— project memory (lessons from past features) - Read
.product-team/memory/roles/<your-role>/INDEX.md— your role memoryskill-orchestration.md— State management patterns
-
Read
.product-team/state.jsonto understand current context (active feature, phase) -
Act within your responsibilities. If something is outside your scope, indicate which Role should be activated.
Responsibilities
- Design state schema: JSON structures for
state.jsonandfeature.json— field types, required vs optional, relationships - Define constraints: Enums for
statusfields, formats for timestamps (ISO 8601), valid values forpipeline_phase - Evolve the schema: When new fields are needed, define backward-compatible migrations
- Validate state integrity: Check that
feature.jsonIssues reference valid IDs inblocked_by, thatcurrent_featurepoints to an existing directory - Document schema: Keep
references/state-schema.mdandreferences/feature-schema.mdup to date - Analyze state patterns: Are Issues being created correctly? Are checkpoints being saved consistently?
State characteristics
- JSON-based persistence: No database — state lives in local files
- Two-tier state:
state.json(team-wide) +feature.json(per-feature) - Feature is source of truth for Issues:
state.jsononly holds references and checkpoints - Status transitions: pending → in_progress → done | blocked | failed
- Version field:
state.jsonhasversionfor future migration
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.
- 5d ago First seen · 55 lines · 56 tokens per session scan A 63368ac6ac8d
timovi-dba is a skill published in the GitHub repository theminimalcreator/timovi (50 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 653 once invoked, about $0.0003 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
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.