agentmods.dev

memory-status

A command that shows where the memory system stores data, which memory areas exist, and how to connect to it.

In plain words
What is it for?
Use it to find the active memory data folder, list its memory databases, check for a conflicting ./lm_data folder, and get connection commands.
Why use it?
It helps you avoid checking the wrong folder when the agent saved memories somewhere else. It also warns about a project folder that can make this mistake easy to miss.

Command

47 25d ago A scan 21 tokens original Apache-2.0
View the source file Wuesteon/lean-memory
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.

agentmods
npx agentmods add commands/wuesteon/lean-memory/memory-status
Clone the repo
git clone --depth 1 https://github.com/Wuesteon/lean-memory
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00021 $0.00437
Opus 5 $0.00010 $0.00218
Sonnet 5 $0.00004 $0.00087
Haiku 4.5 $0.00002 $0.00044

Measured 2d ago against content hash a0c6dd165ea3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

memory-status 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.

plugin/commands/memory-status.md · 36 lines

What it actually says

Report where memory actually lives and how to connect, so the human never inspects an empty root while the agent wrote elsewhere.

  1. Print the resolved data root (the console applies --root > LM_DATA_ROOT > ~/.lean_memory):

    !echo "Resolved root: ${LM_DATA_ROOT:-$HOME/.lean_memory}"

    Then enumerate namespace .db files under that root (skipping _*.db):

    !ls -1 "${LM_DATA_ROOT:-$HOME/.lean_memory}"/*.db 2>/dev/null | grep -v '/_' || echo "(no namespaces yet)"

  2. ./lm_data mismatch warning. The core engine's own default root is ./lm_data, not ~/.lean_memory. If ./lm_data exists in the current project but is not the served root, the human would silently inspect an empty root. Warn when it exists:

    !test -d ./lm_data && echo "WARNING: ./lm_data exists here. Your agent may have written memories to ./lm_data (the engine's default root), not ${LM_DATA_ROOT:-$HOME/.lean_memory}. Run '/memory:ui' with --root ./lm_data to inspect it." || echo "No ./lm_data in this directory."

  3. Connect snippets.

    • Local observing MCP (this plugin already wires it via .mcp.json): uvx lean-memory-console mcp
    • Open the console: /memory:ui
    • Docker HTTP (after /memory:server-up): 
      claude mcp add --transport http lean-memory http://127.0.0.1:8377/mcp \
  --header "Authorization: Bearer $LM_API_KEY"

Guidance: use one namespace per project/session — cross-process writers on a single namespace serialize via retry, not a lock manager.

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. 2d ago First seen · 36 lines · 21 tokens per session scan A a0c6dd165ea3

Subscribe to this mod's changes

memory-status is a command published in the GitHub repository Wuesteon/lean-memory (47 stars, last pushed 25d ago), licensed Apache-2.0. It adds 21 tokens to every session and 437 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.

Memory and context
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens