Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Zenetusken/consolidate-memory/plugin install consolidate-memoryWrote 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.
[](https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-data)<a href="https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-data"><img src="https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-data/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.
<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="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00023 | $0.00404 |
| Opus 5.5 | $0.00009 | $0.00162 |
| Sonnet 5.5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 1mo 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.
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. 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.
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.
- 1mo ago Changed 10e56910957e
- 2mo ago Changed 8f019a98608e
- 2mo ago First seen · 25 lines · 23 tokens per session scan C b4317f6fb77b
cm-data is a command published in the GitHub repository Zenetusken/consolidate-memory (7 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 404 once invoked, about $0.0001 per session on Opus 5.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.
cm-data compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cm-dataZenetusken/consolidate-memory | Command | 7 | 1mo ago | MIT | C | 23 | Claude Code |
| remembrall-helpcukas/remembrall | Command | 6 | 3d ago | MIT | A | 17 | Claude Code |
| budgetcukas/remembrall | Command | 6 | 3d ago | MIT | A | 13 | Claude Code |
| handoffse4thvin/context-handoff | Command | 1 | 5mo ago | MIT | A | 14 | Claude Code |
| recall-maintaindavegoldblatt/total-recall | Command | 202 | 8mo ago | none | A | 0 | Claude Code |
| recall-init-idsdavegoldblatt/total-recall | Command | 202 | 8mo ago | none | A | 0 | Claude Code |
| recall-initdavegoldblatt/total-recall | Command | 202 | 8mo ago | none | A | 0 | Claude Code |