csm-recall

csm-recall is a command for Claude Code from NovasPlace/CSM. It costs 12 tokens per session (222 once invoked), scanned A, original, MIT.

A command for searching project memory and collecting relevant evidence for the current task. It checks remembered claims against the current files, tests, and instructions.

In plain words
What is it for?
Use it to find prior project context, widen the search when results are sparse, and summarize only information that affects the next step.
Why use it?
It helps recover useful decisions and lessons from earlier sessions without treating old memory as more reliable than the workspace.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cross-session-memory plugin — 2 skills, 12 commands, 3 agents shipped together

Good fit Use it to find prior project context, widen the search when results are sparse, and summarize only information that affects the next step.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/novasplace/csm/csm-recall
Install

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.

Clone the repo
git clone --depth 1 https://github.com/NovasPlace/CSM

Made for: Claude Code.

Or install cross-session-memory, the plugin that ships this one along with the rest of its 2 skills, 12 commands, 3 agents.

Wrote 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.

agentmods badge for csm-recall

README.md
[![agentmods](https://agentmods.dev/badge/commands/novasplace/csm/csm-recall/github.svg)](https://agentmods.dev/commands/novasplace/csm/csm-recall)
Your own site
<a href="https://agentmods.dev/commands/novasplace/csm/csm-recall"><img src="https://agentmods.dev/badge/commands/novasplace/csm/csm-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.

agentmods 80×15 button for csm-recall

Your own site · 80×15
<a href="https://agentmods.dev/commands/novasplace/csm/csm-recall"><img src="https://agentmods.dev/badge/commands/novasplace/csm/csm-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00222
Opus 5 $0.00006 $0.00111
Sonnet 5 $0.00002 $0.00044
Haiku 4.5 $0.00001 $0.00022

Measured 9d ago against content hash c48dded8f62a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

csm-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 9d 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.

plugins/cross-session-memory/commands/csm-recall.md · 14 lines

What it actually says

Recall relevant Cross-Session Memory for: $ARGUMENTS

  1. Resolve projectRoot to the absolute root of the current workspace and keep every call scoped to it.
  2. Call csm_memory_search with the topic above (or the current task if no argument was given).
  3. If results are thin, widen with csm_memory_context and csm_memory_related; pull reusable lessons with recall_lessons.
  4. Verify every recalled claim against the current files, tests, and user instructions before acting on it — the workspace is the source of truth, not memory.
  5. Summarize only the evidence that changes what we do next. Do not dump raw records.
Changes

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.

  1. 9d ago First seen · 14 lines · 12 tokens per session scan A c48dded8f62a

Subscribe to this mod's changes

csm-recall is a command published in the GitHub repository NovasPlace/CSM (42 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 222 once invoked, about $0.0001 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-30.