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/open-latch/latchWrote 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/open-latch/latch/latch-decay)<a href="https://agentmods.dev/commands/open-latch/latch/latch-decay"><img src="https://agentmods.dev/badge/commands/open-latch/latch/latch-decay/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/open-latch/latch/latch-decay"><img src="https://agentmods.dev/badge/commands/open-latch/latch/latch-decay.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.00013 | $0.00236 |
| Opus 5.5 | $0.00005 | $0.00094 |
| Sonnet 5.5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
latch-decay 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
Run the weekly maintenance pass on the per-project knowledge base under
<KB_HOME>. Two operations:
- Decay — multiply every referenced node's
ref_countby 0.9 (floored at 1 once any node has been referenced at least once). - Promote — nodes in
status='staging'withref_count >= 3are promoted tostatus='canonical'.
This is the signal loop that makes access-frequency the source of truth for what matters: nodes that are actually consulted keep their weight; nodes that quietly stopped being useful fade.
Run with the Bash tool:
python "<KB_HOME>/src/latch/pipeline/maintenance.py" "$(pwd)"
Report back the decayed_rows count, promoted_count, and the list of
promoted_ids (with titles via latch_get if the user wants to see what got
promoted).
If anything fails, check <KB_HOME>/maintenance.log.
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 Changed b08799823693
- 1mo ago First seen · 28 lines · 13 tokens per session scan A 1deab17b357f
latch-decay is a command published in the GitHub repository open-latch/latch (9 stars, last pushed 5d ago), licensed Apache-2.0. It adds 13 tokens to every session and 236 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-08-31.
Other commands, from other repositories
ctx
Search agent history or trace code to its original agent session.
krimto-status
Show the current state of Krimto memory — total facts, scope breakdown, recent writes, and index health.
context-save
Save project context, decisions, and progress for a later session.
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
save-session-learnings
Document session learnings to CLAUDE.md and AGENTS.md. Use after completing significant tasks, debugging sessions, or discovering project patterns.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.