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/wang1051992187/kireo-mcp-serverWrote 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/wang1051992187/kireo-mcp-server/resume)<a href="https://agentmods.dev/commands/wang1051992187/kireo-mcp-server/resume"><img src="https://agentmods.dev/badge/commands/wang1051992187/kireo-mcp-server/resume/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/wang1051992187/kireo-mcp-server/resume"><img src="https://agentmods.dev/badge/commands/wang1051992187/kireo-mcp-server/resume.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.00017 | $0.00237 |
| Opus 5.5 | $0.00007 | $0.00095 |
| Sonnet 5.5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
resume 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 1mo 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
/kireo:resume
Identify the project
Call project_info and show its key and source so the user can check the project identity.
Load context
Call context_load and display the returned text without paraphrasing, reordering or dropping group headings.
Display the text returned by context_load without reordering or dropping sections. Its order is Constraints → Open threads → Decisions → Gotchas → Key files → Preferences.
Keep the code-index freshness line: it tells the user whether the index exists and how old it is.
Explain markers accurately: [uncertain] means the original evidence was not verified, so do not present it as confirmed fact. [stale] means an open thread has not changed for over 90 days; it may no longer apply, but it is not necessarily false.
An empty project is normal. Explain that no structured context has been saved and suggest the save command. It is not a loading failure. Preserve stored content and use English for operational guidance by default, unless the user requests another language.
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.
- 1mo ago First seen · 23 lines · 17 tokens per session scan A de053de48ac0
resume is a command published in the GitHub repository wang1051992187/kireo-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 237 once invoked, about $0.0001 per session on Opus 5.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-09-14.
Other commands, from other repositories
recall
Recall relevant EverMe memories from past sessions and use them as context for the current task.
reason
Think through a question using memory-backed retrieval.
recall
Semantic + metadata search across stored drawers.
remember
Store a verbatim memory drawer in the current wing.
krimto-status
Show the current state of Krimto memory — total facts, scope breakdown, recent writes, and index health.
tree-ring-capture
Capture a concise validated lesson decision warning or preference in Tree Ring Memory.