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/cbuntingde/kimi-memory/list-memoriesgit clone --depth 1 https://github.com/cbuntingde/kimi-memoryWrote 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/cbuntingde/kimi-memory/list-memories)<a href="https://agentmods.dev/commands/cbuntingde/kimi-memory/list-memories"><img src="https://agentmods.dev/badge/commands/cbuntingde/kimi-memory/list-memories.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.1 | $0.00014 | $0.00322 |
| Opus 5 | $0.00007 | $0.00161 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
list_memories 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
/kimi-memory:list_memories
List the durable memory entries currently on file for the active project.
Steps:
- Call
memory_listwithcwdset to the project root andscopechosen by what the user asked:- unqualified listing or "list memories" →
scope: "all"(project + global; project first). - "list project memories" / "list this project's memories" →
scope: "project". - "list global memories" / "list cross-project memories" →
scope: "global".
- unqualified listing or "list memories" →
- Print a short, readable summary: each entry's scope, id, type, title, and
updated_at. - If the user wants a topic, also call
memory_recallwith the same scope (defaultall) and the topic.
Example (scope: "all"):
- [project] [semantic] ab12cd34ef56… Coding style: tabs, no semicolons (2026-07-27)
- [project] [procedural] 99887766aabb… Deploy: push to main, CI ships (2026-07-25)
- [global] [semantic] fe34ab12cd56… User prefers dark mode (2026-07-26)
The plugin's /list_memories skill is equivalent; this command is the namespaced fallback (/kimi-memory:list_memories).
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 · 28 lines · 14 tokens per session scan A 56c0979203b4
list_memories is a command published in the GitHub repository cbuntingde/kimi-memory (0 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 322 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
iai-directive
Record a standing order the user typed themselves, as an explicit memory directive.
arrecall
AgentRecall on-demand recall — surface past fixes, decisions, and patterns mid-session without leaving your flow.
tree-ring-capture
Capture a concise validated lesson decision warning or preference in Tree Ring Memory.
tree-ring-audit
Audit consolidate or forget stale sensitive or superseded Tree Ring Memory entries.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.