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 commands/korjwl1/toki/bump-schemagit clone --depth 1 https://github.com/korjwl1/tokiWrote 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/commands/korjwl1/toki/bump-schema)<a href="https://agentmods.dev/commands/korjwl1/toki/bump-schema"><img src="https://agentmods.dev/badge/commands/korjwl1/toki/bump-schema.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.00000 | $0.00194 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
bump-schema 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 4d 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.
What it actually says
Bump the DB schema version after a structural change.
When to use
Run this command after modifying any of the following:
StoredEventstruct fields (src/common/types.rs)- Existing event-DB key/value encoding or keyspace layout in
Database::open(src/db.rs) - Dictionary encoding format (src/db.rs)
- Checkpoint format (src/checkpoint.rs)
- Any change that makes existing serialized data incompatible with new code
Instructions
- Read
src/db.rsand find the currentSCHEMA_VERSIONconstant - Increment it by 1
- Commit with message:
chore: bump schema version to {NEW_VERSION}
This resets only the rebuildable <provider>.fjall event databases on next
daemon start. It must not reset <provider>.windows.fjall: window history has
its own WINDOWS_SCHEMA_VERSION and may not be reconstructable.
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.
- 4d ago First seen · 21 lines · 0 tokens per session scan A ca7cfd1c29cd
bump-schema is a command published in the GitHub repository korjwl1/toki (21 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 194 tokens. 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
volume-admin-set-status
Changes the operational status of a named volume.
tokenless-stats
Show Tokenless compression statistics.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.