stats

A command for showing statistics about a stored memory system. It reports how much information is stored, cached, and used.

In plain words
What is it for?
Checking memory counts, cache use, disk usage, recall misses, mining activity, and possible maintenance actions.
Why use it?
It helps you see whether the memory system is full, underused, missing frequently needed information, or waiting for patterns to be reviewed.

Command for Claude Code

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/michael-denyer/memory-mcp/stats
Clone the repo
git clone --depth 1 https://github.com/michael-denyer/memory-mcp

Made for: Claude Code.

Per session 3 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 161 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.00003 $0.00161
Opus 5 $0.00002 $0.00081
Sonnet 5 $0.00001 $0.00032
Haiku 4.5 $0.00000 $0.00016

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

Security

Grade A, and why

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

.claude-plugin/commands/stats.md · 21 lines

What it actually says

Display comprehensive statistics about the memory system.

Use mcp__memory__memory_stats to retrieve and present:

  • Total memories by type (project, pattern, reference, conversation, episodic)
  • Hot cache size and utilization
  • Storage size on disk

Optionally also show:

  • mcp__memory__hot_cache_status for hot cache details
  • mcp__memory__metrics_status for operational metrics
  • mcp__memory__mining_status for pattern mining stats

Suggest actions based on stats:

  • Many memories but empty hot cache? Run /memory-mcp:bootstrap
  • High recall miss rate? Consider promoting frequent memories
  • Many pending mining candidates? Run /memory-mcp:review-mining
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 · 21 lines · 3 tokens per session scan A 1dca0c55029a

Subscribe to this mod's changes

stats is a command published in the GitHub repository michael-denyer/memory-mcp (7 stars, last pushed 14d ago), licensed MIT. It adds 3 tokens to every session and 161 once invoked, about $0.0000 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.