A command for inspecting, exporting, compacting, or purging data created by a consolidate-memory plugin. It distinguishes that data from Claude's separate built-in memory.

Use it to inventory or export plugin data, compact journals, and deliberately purge selected plugin-data scopes.

It helps you understand where plugin data is stored and manage its size without accidentally removing Claude's native memory.

cm-data — Command for coding agents by Zenetusken: A command for inspecting, exporting, compacting, or purging data…

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/zenetusken/consolidate-memory/cm-data

Clone the repo

git clone --depth 1 https://github.com/Zenetusken/consolidate-memory

Or install consolidate-memory, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-data.svg)](https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-data)

Your own site

<a href="https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-data"><img src="https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-data.svg" alt="Measured on agentmods" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 393 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00023	$0.00393
Opus 5	$0.00012	$0.00197
Sonnet 5	$0.00005	$0.00079
Haiku 4.5	$0.00002	$0.00039

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

Security

Grade C, and why

cm-data scanned grade C with 1 finding 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 today.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

Operational data lives under plugin-data. Native `~/.claude/projects/<slug>/memory` is also Claude Auto Memory — do not `rm -rf` it to uninstall this plugin.

plugins/consolidate-memory/commands/cm-data.md · 25 lines

What it actually says

Operational data lives under plugin-data. Native ~/.claude/projects/<slug>/memory is also Claude Auto Memory — do not rm -rf it to uninstall this plugin.

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data inventory --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data export --project . --dest /tmp/cm-export
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data compact --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py journal inventory --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py journal compact --project . --apply --confirm journal-compact
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data purge --scope managed-mirrors --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data purge --scope managed-mirrors --apply --confirm purge-managed-mirrors --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data purge --scope project-ops --apply --confirm purge-project-ops --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data purge --scope domain-canonicals --apply --confirm purge-domain-canonicals --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data purge --scope all-plugin-data --apply --confirm purge-all-plugin-data --project .
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py data retention --project .

Show the plan first. Purge never deletes Claude's native Auto Memory (~/.claude/projects/<slug>/memory authored files). Export is a tar.gz + sha256 manifest of plugin-data only.

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.

today First seen · 25 lines · 23 tokens per session scan C b4317f6fb77b

Subscribe to this mod's changes

cm-data is a command published in the GitHub repository Zenetusken/consolidate-memory (6 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 393 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Memory and context ai-agents claude-code claude-code-plugin context-management

cm-data

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade C, and why

Recursive force deletehighDestructive command

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

remember

evolution

smartcompact

recall

reindex

topics