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/rand/mnemosyne/memory-searchgit clone --depth 1 https://github.com/rand/mnemosyneWhat 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.00013 | $0.00643 |
| Opus 5 | $0.00006 | $0.00321 |
| Sonnet 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 2d 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.
- 2d ago First seen · 84 lines · 13 tokens per session scan A 73e12d8327f5
memory-search is a command published in the GitHub repository rand/mnemosyne (84 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 643 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-30.
Other commands, from other repositories
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
hatch3r-debug
Standalone debug-and-fix workflow — add strategic debug logging, collect runtime logs from the user, perform root cause analysis, implement the fix, and clean up all debug artifacts.
hatch3r-feature-plan
Design a new capability -- draft user stories, acceptance criteria, data model, API surface, and sub-issue breakdown as an epic-shaped todo.md for greenfield features.
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
hatch3r-incident-response
Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents.