agentmods.dev

memos

A command that opens a local, read-only web dashboard showing the contents of Kimi's memory databases in your default browser.

In plain words
What is it for?
Use it to open the memory dashboard after its companion app is running and review saved memory entries.
Why use it?
It gives you a visual way to inspect stored agent memory without querying the databases directly.

Command

0 2d ago A scan 29 tokens original MIT
View the source file cbuntingde/kimi-memory
Install

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.

agentmods
npx agentmods add commands/cbuntingde/kimi-memory/memos
Clone the repo
git clone --depth 1 https://github.com/cbuntingde/kimi-memory
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 536 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00536
Opus 5 $0.00015 $0.00268
Sonnet 5 $0.00006 $0.00107
Haiku 4.5 $0.00003 $0.00054

Measured yesterday against content hash 8c8e8f741514, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

memos scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- curl with a 2-second timeout, or `Test-NetConnection 127.0.0.1 -Port 8765`
commands/memos.md · 42 lines

What it actually says

/kimi-memory:memos

Open the local kimi-memos-dashboard in the user's default browser. The dashboard runs as a standalone companion app under ~/.kimi-code/plugins/managed/kimi-memos-dashboard/ and is intentionally NOT a Kimi plugin (per its own AGENTS.md) — this slash command is a thin integration, not a control surface.

Steps:

  1. Probe whether http://127.0.0.1:8765/ is responding (HEAD request via Bash
    • curl with a 2-second timeout, or Test-NetConnection 127.0.0.1 -Port 8765 on PowerShell).
  2. If not responding, tell the user: kimi-memos-dashboard is not running. Start it with: cd ~/.kimi-code/plugins/managed/kimi-memos-dashboard && npm start and then re-run /memos. Do not start it for them — the dashboard binds a port and the user should opt in.
  3. If responding, open the dashboard URL in the default browser:
    • Windows (Git Bash / cmd): start "" "http://127.0.0.1:8765/"
    • Windows (PowerShell): Start-Process "http://127.0.0.1:8765/"
    • macOS: open "http://127.0.0.1:8765/"
    • Linux: xdg-open "http://127.0.0.1:8765/"
  4. Report the URL back to the user.

Notes:

  • The dashboard reads the same SQLite files that this plugin writes to, with PRAGMA query_only=ON enforced, so opening it cannot mutate memory data.
  • The dashboard binds 127.0.0.1 by default; LAN exposure is not provided here.
  • Optional bearer-token auth is respected by the dashboard itself; this command does not bypass it.
  • The default port (127.0.0.1:8765) and token scheme are owned by kimi-memos-dashboard, not by this plugin. If the dashboard re-binds or changes its auth, the probe in step 1 will return a connection error and the user must adjust the URL or restart the dashboard before re-running /kimi-memory:memos.
Changes

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.

  1. yesterday First seen · 42 lines · 29 tokens per session scan A 8c8e8f741514

Subscribe to this mod's changes

memos is a command published in the GitHub repository cbuntingde/kimi-memory (0 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 536 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metricsCode reviewMemory and contextagent-memoryai-codingkimi-codekimi-pluginlocal-firstmcp-server
Related

Other commands, from other repositories

tree-ring-capture

Capture a concise validated lesson decision warning or preference in Tree Ring Memory.

TerminallyLazy/Tree-Ring-Memory · 13 tokens

tree-ring-audit

Audit consolidate or forget stale sensitive or superseded Tree Ring Memory entries.

TerminallyLazy/Tree-Ring-Memory · 13 tokens

tree-ring-update

Check for or install a verified Tree Ring Memory CLI update without changing installation scope.

TerminallyLazy/Tree-Ring-Memory · 15 tokens

tree-ring-certify

Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.

TerminallyLazy/Tree-Ring-Memory · 17 tokens

tree-ring-dox-sync

Preview and synchronize DOX-style AGENTS.md guidance as source-linked Tree Ring memory.

TerminallyLazy/Tree-Ring-Memory · 16 tokens

tree-ring-recall

Recall durable Tree Ring Memory context before starting or resuming work.

TerminallyLazy/Tree-Ring-Memory · 12 tokens