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/xcodethink/open-claude-code-skills/recallgit clone --depth 1 https://github.com/xcodethink/open-claude-code-skillsWrote 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/xcodethink/open-claude-code-skills/recall)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/recall"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/recall.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00411 |
| Opus 5 | $0.00018 | $0.00205 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
recall 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 3d 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
调取记忆
用户想从本地记忆系统中调取信息。按以下步骤操作：
1. 解析关键词
从用户的输入中提取核心搜索词。如果用户的话很模糊，主动识别关键词。
2. 调用 memory_search
使用 MCP 工具 memory_search 进行搜索。这会自动按当前项目 wing + global wing 隔离。
参数：
query: 提取的关键词limit: 默认 5
3. 解读结果
- 相似度 ≥ 0.7（强相关） → 当作权威依据回答
- 相似度 0.5-0.7（中相关） → 参考但提示可能不准
- 相似度 < 0.5 → 视为"未找到"，告诉用户没有相关记忆
4. 必要时跨项目搜索
如果当前项目 + global 都没找到，问用户是否需要跨项目搜索。
得到确认后用 memory_search_all。
5. 警示规则
如果搜索结果出现非当前项目的内容（即使是 memory_search 范围内），必须警示： "此结果来自 [其他项目]，配置细节请勿直接复用，只能借鉴模式。"
6. 输出格式
找到 X 条相关记忆：
[强相关 0.78] 来自 [wing]/[文件名]
内容摘要...
[中相关 0.62] 来自 [wing]/[文件名]
内容摘要...
是否需要更多细节，或跨项目搜索更多结果？
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.
- 3d ago First seen · 51 lines · 36 tokens per session scan A f1dad2e8404c
recall is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 28d ago), licensed MIT. It adds 36 tokens to every session and 411 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 commands, from other repositories
memstack-search
Search MemStack memory for past sessions, insights, and project context.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
memory-consent
Grant or revoke consent for session-end auto-memorize. Usage: /memory-consent yes|no|ask.
learn
Learn Claude Code best practices and capture lessons into persistent memory.
record
Record a new architectural decision into project memory.
context
Retrieve relevant decisions from project memory for the current task.