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.
git clone --depth 1 https://github.com/krimto-labs/krimtoWrote 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/krimto-labs/krimto/krimto-status)<a href="https://agentmods.dev/commands/krimto-labs/krimto/krimto-status"><img src="https://agentmods.dev/badge/commands/krimto-labs/krimto/krimto-status/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/commands/krimto-labs/krimto/krimto-status"><img src="https://agentmods.dev/badge/commands/krimto-labs/krimto/krimto-status.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.00135 |
| Opus 5 | $0.00014 | $0.00068 |
| Sonnet 5 | $0.00006 | $0.00027 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
krimto-status 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 12d 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
Show the user a summary of Krimto's current state:
- Call
krimto_list_scopesto get scope counts. - Call
git logon the Krimto storage directory for recent activity. - Format as a clean status report:
## Krimto Status
Scopes: N user, M team, K org
Total facts: T
Recent writes: (last 5 timestamps)
Index status: synced / out-of-sync
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.
- 12d ago First seen · 21 lines · 28 tokens per session scan A 171a67d0b03a
krimto-status is a command published in the GitHub repository krimto-labs/krimto (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 135 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 commands, from other repositories
tl-export
Export thoughtline memories to a markdown file the user can review or commit.
tl-search
Search thoughtline memories by keyword or topickey GLOB.
tl-recent
Show the most recent thoughtline memories for the active project.
tl-stats
Summarize the thoughtline memory store for the active project.
latch-compact
Manually trigger a latch compaction for the current session.
latch-tree
Rebuild the hierarchical cluster/summary tree for this project's KB.