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.
git clone --depth 1 https://github.com/ConradLu2740/ProactiveAgentWrote 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/conradlu2740/proactiveagent/recall)<a href="https://agentmods.dev/commands/conradlu2740/proactiveagent/recall"><img src="https://agentmods.dev/badge/commands/conradlu2740/proactiveagent/recall/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/conradlu2740/proactiveagent/recall"><img src="https://agentmods.dev/badge/commands/conradlu2740/proactiveagent/recall.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.00009 | $0.00078 |
| Opus 5.5 | $0.00004 | $0.00031 |
| Sonnet 5.5 | $0.00002 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
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 1mo 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
调用 mcp__proactive-agent__memory_recall 查询与以下内容相关的记忆，带 1-3 个关键词，并简要汇报（类型 / 重要度 / 原文）：
$ARGUMENTS
如果结果为空，说明没有相关记忆，不要编造。
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.
- 1mo ago First seen · 10 lines · 9 tokens per session scan A 8d4f20e9b1ac
recall is a command published in the GitHub repository ConradLu2740/ProactiveAgent (2 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 78 once invoked, about $0.0000 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-31.
Other commands, from other repositories
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
recall
Recall durable project context for a concrete question.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.