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 skills/zehee/kimi-code-memory-mcp-server/memory-managenpx skills add Zehee/kimi-code-memory-mcp-server --skill memory-managegit clone --depth 1 https://github.com/Zehee/kimi-code-memory-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/skills/zehee/kimi-code-memory-mcp-server/memory-manage)<a href="https://agentmods.dev/skills/zehee/kimi-code-memory-mcp-server/memory-manage"><img src="https://agentmods.dev/badge/skills/zehee/kimi-code-memory-mcp-server/memory-manage.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 | $0.00021 | $0.00653 |
| Opus 5 | $0.00010 | $0.00327 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
memory-manage 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 3d 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
记忆工具调度提示
本 Skill 是轻量提醒。当用户意图匹配上述任一情况时，调用对应的 mcp__kimi-memory__* 工具。
快速映射
| 用户意图 | 工具 |
|---|---|
| "记住…" / "保存…" | mcp__kimi-memory__remember |
| "读取…" / "看看…" | mcp__kimi-memory__recall |
| "搜索记忆…" | mcp__kimi-memory__search |
| "列出记忆/标签" | mcp__kimi-memory__list / mcp__kimi-memory__list_tags |
| "移动/归档…" | mcp__kimi-memory__move |
| "删除…" | mcp__kimi-memory__delete |
| "整理记忆" | mcp__kimi-memory__organize_memories |
| "同步索引" | mcp__kimi-memory__sync_workspace_index |
| "搜索历史对话" | mcp__kimi-memory__search_context |
| "加载第 N 轮" | mcp__kimi-memory__load_turn_context |
| "查看搜索视图" | mcp__kimi-memory__list_search_views |
| "关联到主题" | mcp__kimi-memory__tag_theme |
| "追溯主题" | mcp__kimi-memory__trace_theme |
| "列出主题" | mcp__kimi-memory__list_themes |
| "手动精炼轮次" | mcp__kimi-memory__refine_session_turns |
行为规范（何时 remember、决策守卫、主题追溯协议）见 AGENTS.md。
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.
- 3d ago First seen · 44 lines · 21 tokens per session scan A babb22486c4f
memory-manage is a skill published in the GitHub repository Zehee/kimi-code-memory-mcp-server (2 stars, last pushed 15d ago), licensed MIT. It adds 21 tokens to every session and 653 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…