Borrowing it
Nothing to install: this file belongs to rand/mnemosyne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rand/mnemosyne/main/.claude/commands/memory-search.mdgit clone --depth 1 https://github.com/rand/mnemosyneWrote 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/rand/mnemosyne/memory-search)<a href="https://agentmods.dev/commands/rand/mnemosyne/memory-search"><img src="https://agentmods.dev/badge/commands/rand/mnemosyne/memory-search/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/rand/mnemosyne/memory-search"><img src="https://agentmods.dev/badge/commands/rand/mnemosyne/memory-search.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.00643 |
| Opus 5.5 | $0.00005 | $0.00257 |
| Sonnet 5.5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
memory-search 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
I will search Mnemosyne memories and display formatted results.
Usage:
/memory-search <query>- Search with defaults/memory-search --namespace <ns> <query>- Filter by namespace/memory-search --min-importance <1-10> <query>- Filter by minimum importance/memory-search --limit <N> <query>- Limit number of results/memory-search --no-graph <query>- Disable graph expansion
Instructions for me:
-
Parse the arguments:
- Extract
--namespaceflag if present (otherwise auto-detect) - Extract
--min-importanceflag if present - Extract
--limitflag if present (default: 10) - Extract
--no-graphflag if present (default: expand_graph = true) - The remaining text is the search query
- Extract
-
Auto-detect namespace (if not specified):
- Use Bash to check git root:
git rev-parse --show-toplevel 2>/dev/null - Read CLAUDE.md for project name
- Construct namespace as
project:<name> - If no project: search all (
nullnamespace)
- Use Bash to check git root:
-
Call Mnemosyne MCP tool:
{ "name": "mnemosyne.recall", "arguments": { "query": "<search query>", "namespace": "<namespace or null>", "max_results": <limit>, "min_importance": <min_importance or null>, "expand_graph": <true/false> } } -
Format the output: For each result, display:
Found <count> memories matching "<query>": <for each result, numbered>: <number>. [<importance stars>/10] <memory_type> Created: <date> Summary: <summary> Match: <match_reason> (score: <score>) <content preview (first 200 chars)>... Tags: <tags>Where:
- Importance stars: ⭐ repeated times
- Memory type: ArchitectureDecision, CodePattern, BugFix, etc.
- Date: formatted as YYYY-MM-DD
- Match reason: from the search result
- Score: formatted to 2 decimal places
If no results:
No memories found matching "<query>" Suggestions: - Try different keywords - Remove namespace filter to search globally - Lower min-importance threshold - Check if memories exist: /memory-list -
Error handling:
- If MCP server not available: "Error: Mnemosyne MCP server not running"
- If query is empty: "Error: No search query provided. Usage: /memory-search "
Please search for memories using the provided arguments.
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 First seen · 84 lines · 13 tokens per session scan A 73e12d8327f5
memory-search is a command published in the GitHub repository rand/mnemosyne (101 stars, last pushed 11mo ago), licensed MIT. It adds 13 tokens to every session and 643 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-30.
Other commands, from other repositories
diagnose-synapse
Run a comprehensive diagnostic of the SYNAPSE context engine, comparing expected vs. actual pipeline state, including session performance analysis with exact timing data.
memory
Read-side memory operations on the knowledge graph: search past decisions and patterns, load session context, view decision timelines, render Mermaid graph visualizations. Subcommands: search, load, history, viz, status. Use when finding or reviewing what memory already holds. For storing new knowledge instead, invoke…
compact-prep
Ask the agent to prepare for conversation compaction by updating any relevant state and providing guidance for the compaction agent and to kick off the session there after.
greet
Generate contextual agent greeting using GreetingBuilder infrastructure.
add-rule
Adds a new rule to an existing SYNAPSE domain file.
toggle-domain
Toggles a SYNAPSE domain between active and inactive in the manifest.