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/jansenanalytics/claudex/memory-searchnpx skills add JansenAnalytics/claudex --skill memory-searchgit clone --depth 1 https://github.com/JansenAnalytics/claudexWhat 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.00058 | $0.00700 |
| Opus 5 | $0.00029 | $0.00350 |
| Sonnet 5 | $0.00012 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Search — Semantic RAG
You have a vector memory search system that indexes:
- Your own memory files (CLAUDE.md, memory/*.md)
- Your Telegram conversation transcripts
- Cross-agent memories from Kite, Poe, and Argus (OpenClaw agents)
When to Search
ALWAYS search before answering about:
- Prior work, decisions, or conversations
- Dates, timelines, project history
- People, preferences, or context from past sessions
- Anything the user says "remember" or "we discussed"
- Cross-agent context ("what has Argus been working on?")
How to Search
# Basic search
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "your query here"
# Filter by source (memory files only, sessions only, cross-agent only)
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --source memory
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --source session
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --source cross-agent
# Filter by agent
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --agent kite
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --agent argus
# More results
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --limit 15
# JSON output (for parsing)
node --experimental-sqlite ~/.claude-agent/scripts/memory-search.cjs --search "query" --json
Interpreting Results
Each result shows:
- Source:
memory(your files),session(conversation transcripts),cross-agent(Kite/Poe/Argus) - Agent: which agent's data (claudex, kite, poe, argus)
- Score: hybrid of vector similarity (0.7) + text match (0.3), with recency decay
- Snippet: first 500 chars of the matched chunk
Higher scores = more relevant. Results above 0.3 are usually meaningful.
Reindexing
The index updates automatically via cron (every 30 min). To force a reindex:
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 · 71 lines · 58 tokens per session scan A 180e4e720c9c
memory-search is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 700 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…