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 krimto-labs/krimto --skill krimto-write-factgit 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/skills/krimto-labs/krimto/krimto-write-fact)<a href="https://agentmods.dev/skills/krimto-labs/krimto/krimto-write-fact"><img src="https://agentmods.dev/badge/skills/krimto-labs/krimto/krimto-write-fact/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/krimto-labs/krimto/krimto-write-fact"><img src="https://agentmods.dev/badge/skills/krimto-labs/krimto/krimto-write-fact.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.00070 | $0.00417 |
| Opus 5 | $0.00035 | $0.00209 |
| Sonnet 5 | $0.00014 | $0.00083 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
krimto-write-fact 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
Writing facts to Krimto memory
When the user wants to save a durable fact:
- Choose the scope (default to the user's personal scope unless the fact is clearly shared):
user/<identity>— personal preferences, individual decisions (e.g.user/[email protected])team/<slug>— team conventions, shared system rules (e.g.team/payments)org/<slug>— company-wide standards (e.g.org/acme); org admins only
- Call
krimto_recallfirst to avoid writing a duplicate. - Call the MCP tool
krimto_writewith:scope: one of the forms abovetitle: a descriptive title, ≤ 80 charactersbody: markdown contenttags(optional): lowercase kebab-case arraysource(optional): URL or stable identifiersupersedes(optional): array of fact ids this replaces
The server assigns the author, timestamps, and fact id, writes the markdown file, and commits to git.
Return the resulting path so the user can find it.
Common mistakes
- Don't write the same fact at multiple scopes. Pick the broadest scope where it is true.
- Don't write to
org/without confirming the user is an org admin. - Don't invent the scope. If unclear, ask, or default to the user's personal scope.
- Don't extract facts silently — only write when the user asks or you learn a durable, non-obvious fact.
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 · 34 lines · 70 tokens per session scan A 1b7b81731a03
krimto-write-fact is a skill published in the GitHub repository krimto-labs/krimto (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 417 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-31.
Other skills, from other repositories
dashboard
Open OwnMem Console, the local dashboard for this repository's memory. Use when the user asks to open the dashboard, see memory metrics, check adoption or recall quality, or set up the optional embedding lane. Requires a repository initialized with the dashboard layer.
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
ultramemory-snapshot
Compose and save a durable, wayback-grade session snapshot to UltraMemory. Use this whenever you are asked to write a session snapshot or rollup of the work just done — in particular when the UltraMemory capture hook nudges you to "Compose a session snapshot per the ultramemory-snapshot Skill rubric ... and save it…
setup
Guides Claude through first-time UltraMemory configuration after plugin install — API key, MCP server registration, test recall, and 401/403 troubleshooting.
ownmem-init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.