Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rjmurillo/ai-agentsnpx agentmods add commands/rjmurillo/ai-agents/memory-searchWrote 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/rjmurillo/ai-agents/memory-search)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/memory-search"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/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/rjmurillo/ai-agents/memory-search"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/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.00024 | $0.00414 |
| Opus 5.5 | $0.00010 | $0.00166 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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 2mo 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
Interface Selection: This is the CLI interface. See Memory Interface Decision Matrix for when to use other interfaces.
Search the Forgetful knowledge base for relevant memories.
Your Task
Perform a semantic search using execute_forgetful_tool("query_memory", {...}) with the user's query.
Query: $ARGUMENTS
Search Parameters
Use these parameters for the search:
{
"query": "<user's search query>",
"query_context": "User initiated search via /memory-search command",
"k": 5,
"include_links": true,
"max_links_per_primary": 3
}
If the query mentions a specific project, add project_ids filter.
Response Format
Present results clearly:
- Summary: Brief overview of what was found (or "No relevant memories found")
- Primary Memories: For each memory show:
- Title (with importance score)
- Key content snippet
- Tags
- Linked memories if relevant
- Suggestions: If results seem incomplete, suggest refining the query or creating a new memory
Example
User: /memory-search authentication patterns
You search and respond:
Found 3 memories about authentication patterns:
1. **FastAPI JWT Authentication** (Importance: 9)
JWT middleware using httponly cookies for security...
Tags: security, authentication, fastapi
2. **OAuth2 Decision** (Importance: 8)
Chose OAuth2 over API keys for user-facing auth...
Tags: decision, oauth, security
Related: Memory #45 (Session management approach)
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.
- 2mo ago First seen · 67 lines · 24 tokens per session scan A d8b7ca81979c
memory-search is a command published in the GitHub repository rjmurillo/ai-agents (49 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 414 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
load-session
Load a synced session summary for context.
cs-internal-comms
Internal-only change-management comms using ADKAR (Prosci) + Kotter's 8-step. NOT marketing (external) and NOT executive narrative strategy. Direct invocation of the internal-comms skill.
cs-process-map
Map an internal business process (BPMN-style swim lanes), measure cycle time, and detect bottlenecks where work spends most of its time waiting. Direct invocation of the process-mapper skill.
ingest
Ingest source material into an active wiki. Accepts URLs, file paths, PDFs, freeform text, or processes the inbox. Supports tweets via Grok MCP.
rem_help
Each section is printed verbatim by --help for the command it names. The agreed design is issue #1656; change a page there and here together.
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.