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/zilliztech/memsearch/memory-confignpx skills add zilliztech/memsearch --skill memory-configgit clone --depth 1 https://github.com/zilliztech/memsearchWrote 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/zilliztech/memsearch/memory-config)<a href="https://agentmods.dev/skills/zilliztech/memsearch/memory-config"><img src="https://agentmods.dev/badge/skills/zilliztech/memsearch/memory-config.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.00052 | $0.02634 |
| Opus 5 | $0.00026 | $0.01317 |
| Sonnet 5 | $0.00010 | $0.00527 |
| Haiku 4.5 | $0.00005 | $0.00263 |
Grade A, and why
memory-config 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://pypi.org/pypi/memsearch/json \ How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a MemSearch configuration assistant. This skill manages MemSearch settings only. It is not the host agent's built-in memory/config system.
In diagnostic summaries or final answers, state once that this is MemSearch memory configuration, not the host agent's own memory/config system. Do not prepend that sentence to every progress update or every paragraph.
When this skill is triggered, inspect the user's request text. If there is no concrete request, run a diagnostic. If they ask for a specific setting or change, route the request using the flows below.
Which agent am I running as?
This skill is shared by five agent platforms, but platform-specific details
(version-check commands, plugins.<platform>.* keys, native model defaults,
restart guidance) live in per-platform reference files. Read ONLY the one file
matching your current environment:
- Claude Code →
references/claude-code.md - Codex →
references/codex.md - OpenClaw →
references/openclaw.md - OpenCode →
references/opencode.md - DeepSeek Harness →
references/dsh.md
If you are unsure which agent you are, check these environment markers:
DSH_HOME/~/.dsh → DeepSeek Harness; CODEX_HOME/~/.codex → Codex;
~/.openclaw → OpenClaw; ~/.config/opencode → OpenCode;
CLAUDE_PLUGIN_ROOT → Claude Code.
Read that platform file before performing platform-specific diagnosis or configuration. Do not read the other platform files.
Intent Routing
- Empty request or "check": diagnose current MemSearch setup.
- "Show/get setting": read the requested resolved/global/project value.
- "Set/enable/disable/change": choose global vs project scope explicitly; use global config for trusted plugin automation/provider/prompt/endpoint settings and project config only for allowlisted local indexing knobs.
- "Not capturing/search empty/no memory": troubleshoot files, config, and index health.
- "Use OpenAI/Gemini/Anthropic/native/model": configure provider routing.
- "PROJECT.md/USER.md/profile/review": configure advanced maintenance.
- "skill/distill/extract a skill/memory-to-skill": procedural-memory distillation — enable or tune it here, or use the dedicated
memory-to-skillskill to review and install candidates. - "Prompt": explain or configure prompt overrides.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 219 lines · 52 tokens per session scan A ccdc4e83e3eb
memory-config is a skill published in the GitHub repository zilliztech/memsearch (2,559 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 2,634 once invoked, about $0.0003 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-30.
Other skills, from other repositories
install-openviking-memory
Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…
openclaw-plugin
This plugin is a thin adapter between OpenClaw and LycheeMem. It does not replace memory-core, does not claim plugins.slots.memory, and does not duplicate LycheeMem algorithms.
lycheemem
Forceful operating rules for using LycheeMem as the primary structured long-term memory path inside OpenClaw.
memory
Use LycheeMem as Claude Code's structured long-term memory for prior conversations, user preferences, project decisions, timelines, and durable facts.
evolve-lite:provenance
Analyze saved trajectories and recall audit events offline to record whether recalled guidelines influenced completed sessions.
evolve-lite:retention
Apply data-retention rules to the local evolve store — flag or delete stale and unused memories and expired sessions (dry-run by default).