memory-stats

memory-stats is a command for Claude Code from studiomeyer-io/studiomeyer-marketplace. It costs 16 tokens per session (203 once invoked), scanned A, original, MIT.

A command that reports the health of StudioMeyer Memory, including counts, warnings, follow-up items, and relevant sprint information. StudioMeyer Memory is a system for storing knowledge from work sessions.

In plain words
What is it for?
Use it to check learning, decision, entity, and session counts; find stale information or open decisions; and review current blockers or sprint tasks.
Why use it?
It gives you a quick factual overview of what is stored, what may need attention, and whether the system has problems.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the studiomeyer-memory plugin — 2 skills, 11 commands, 1 agent shipped together

Good fit Use it to check learning, decision, entity, and session counts; find stale information or open decisions; and review current blockers or sprint tasks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/studiomeyer-io/studiomeyer-marketplace/memory-stats
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/studiomeyer-io/studiomeyer-marketplace

Made for: Claude Code.

Or install studiomeyer-memory, the plugin that ships this one along with the rest of its 2 skills, 11 commands, 1 agent.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/memory-stats"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/memory-stats.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 203 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.00016 $0.00203
Opus 5 $0.00008 $0.00102
Sonnet 5 $0.00003 $0.00041
Haiku 4.5 $0.00002 $0.00020

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

Security

Grade A, and why

memory-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 4d 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/studiomeyer-memory/commands/memory-stats.md · 16 lines

What it actually says

Give the user a quick health overview of their StudioMeyer Memory.

  1. Call nex_health from the studiomeyer-memory MCP server for current counts and degradation status.
  2. Call nex_proactive for what needs attention: stale learnings, open decisions, knowledge gaps, pattern clusters, skill fail-rates, unfinished tasks, never-read observations, and entries saved without a project.
  3. Optionally call nex_sprint for the current sprint state if it looks active.
  4. Render a compact summary:
    • Counts: total learnings, decisions, entities, sessions
    • Health flags: any degradations, gatekeeper status
    • Top 3 proactive action items with the suggested next-step tool
    • Sprint state if relevant: active tasks, blockers
  5. Stay factual. Do not invent items not returned by the server.
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. 4d ago Changed · +1 tokens per session 0c6ddc49879a
  2. 9d ago First seen · 16 lines · 15 tokens per session scan A 88b80c697de0

Subscribe to this mod's changes

memory-stats is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 203 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-31.