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/helloruru/claude-memory-engine/memory-searchgit clone --depth 1 https://github.com/HelloRuru/claude-memory-engineWhat 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.00000 | $0.00245 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
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
/memory-search -- Search Memory Files
Search across all memory files by keyword.
Usage
/memory-search {keyword}
Steps
-
Identify search scope: Scan these directories for
.mdfiles:~/.claude/projects/{current-project-id}/memory/~/.claude/sessions/diary/~/.claude/skills/learned/~/.claude/sessions/(session summaries)
-
Search: Use Grep to find the keyword across all
.mdfiles in those directories -
Report results:
Memory Search: "{keyword}"
Found {N} matches in {M} files:
{filename}:{line_number} — {matching line preview}
{filename}:{line_number} — {matching line preview}
...
- If no results: suggest related keywords or broader search terms
Notes
- Case-insensitive search
- Show max 20 results, sorted by most recently modified file first
- Truncate long lines to 120 characters
- If the keyword is in Chinese, also search for related terms
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 · 38 lines · 0 tokens per session scan A 1a027f5c6cb0
memory-search is a command published in the GitHub repository HelloRuru/claude-memory-engine (133 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 tokens. 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
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
validate-dependencies
Validate all task dependencies for issues.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.