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/liveevilkin/cortex/memory-searchnpx skills add liveevilkin/Cortex --skill memory-searchgit clone --depth 1 https://github.com/liveevilkin/CortexWhat 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.00049 | $0.00300 |
| Opus 5 | $0.00024 | $0.00150 |
| Sonnet 5 | $0.00010 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
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 — 混合检索
Process
- Parse user query for keywords and intent
- First pass: grep exact keyword match in daily/ + decisions/
- Second pass (if first yields low results): Obsidian REST API semantic search
- Third pass (if context needed): follow [[wikilinks]] from matched files
- Aggregate and present results with source links
Search Strategy
- Specific terms (dates, APIs, names) → grep first (fast, zero tokens)
- Conceptual queries ("what was that decision about...") → REST API search
- Related context ("what else is connected to...") → wikilink graph traversal
Gotchas
- grep search is case-sensitive by default; use
-ifor case-insensitive - Obsidian REST API requires Obsidian to be running
- Daily files are in
Claude-Code-Memory/daily/, decisions inClaude-Code-Memory/decisions/ - User knowledge base is at vault root (个人简历, 面试问答, etc.)
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 · 26 lines · 49 tokens per session scan A e9089a0522c5
memory-search is a skill published in the GitHub repository liveevilkin/Cortex (1 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 300 once invoked, about $0.0002 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…