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/n24q02m/claude-plugins/recall-contextnpx skills add n24q02m/claude-plugins --skill recall-contextgit clone --depth 1 https://github.com/n24q02m/claude-pluginsWrote 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/skills/n24q02m/claude-plugins/recall-context)<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/recall-context"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/recall-context.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.1 | $0.00053 | $0.00793 |
| Opus 5 | $0.00026 | $0.00396 |
| Sonnet 5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
recall-context 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 6d 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.
This is a copy
100% identical to recall-context — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recall Context
Proactive memory retrieval that pulls prior context relevant to the work about to happen. Reduces "starting from scratch" errors and prevents the agent from re-deriving conclusions already captured in mnemo.
When to Use
- Session start: load any preferences, decisions, or open questions tied to the current cwd / project before the user types their first prompt.
- Before a significant decision: surface prior decisions in the same area (e.g. database choice, lint rules, deployment target) so the agent does not contradict an earlier conclusion.
- When the user names a topic: e.g. "let's work on the auth flow" - pull memories tagged or describing auth before proposing a plan.
- After a long context gap: if the conversation referenced earlier decisions but the agent does not have them in working memory, recall them on demand.
Steps
-
Resolve query terms from the trigger:
cwd: use the current working directory path + project name as the query (e.g.mnemo-mcpor/c/Users/.../wet-mcp).recent: use the last 5-10 file paths the agent edited or read.<topic>: use the topic verbatim (the user's words).- Default (no arg): combine cwd + last 3 file paths.
-
Search mnemo with
context_typefiltering when applicable:memory(action="search", query="<resolved query>", context_type=null, limit=10, include_archived=false)- For decisions only: pass
context_type="decision". - For preferences only: pass
context_type="preference". - Without filter, results span all six context types.
- For decisions only: pass
-
Synthesize results into a 2-3 sentence summary grouped by type:
- decisions, preferences, facts, open tasks
- Present to the user as: "From prior sessions: ..."
- Include memory IDs for any item the user might want to update or delete later.
-
Skip silently if mnemo is offline (tool errors), returns 0 results, or only returns low-relevance matches (rerank_score < 0.3). Do not inject noise into the conversation.
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.
- 6d ago First seen · 88 lines · 53 tokens per session scan A 4a6f469a9053
recall-context is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 793 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to recall-context, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
flow-next-memory-migrate
Migrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.
decision-ledger
Maintain an append-only decision ledger (DECISIONS.md). Use when the user confirms a decision, reverses or changes a past decision, asks what was decided and why, or at session start to load standing decisions.
knowledge-base
Keep verified findings in memory/knowledge/ so the same research is never done twice. Use before researching any topic, when a finding passes the verify gate, or when about to answer from something learned in an earlier session.
pin
Turn a correction or working preference the user just expressed into a permanent ballast rule. Use when the user corrects your behavior, says "don't do X" / "always do Y" / "I told you before", or asks you to remember how they want things done.
catchup
Restore context after /clear by summarizing recent work and project state.