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 smrafiz/claude-supercharger/plugin install superchargerWrote 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/smrafiz/claude-supercharger/memory-prune)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/memory-prune"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/memory-prune.svg" alt="Measured on agentmods" 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.00000 | $0.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
memory-prune 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 8d 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.
What it actually says
Archive resolved memory entries so they stop loading into context every session. Arguments: $ARGUMENTS
Claude's file-memory (~/.claude/projects/<project>/memory/) loads its MEMORY.md
index into context at the start of every session. Entries that are done — resolved,
superseded, debunked — keep costing tokens forever. This prunes them safely:
it only auto-archives entries the author explicitly marked status: resolved (or
superseded) with type: project; everything else is only suggested. Nothing is
deleted — entries move to memory/archive/ and can be restored.
Step 1 — show what would happen (default, no changes):
bash ${CLAUDE_PLUGIN_ROOT}/tools/memory-prune.sh
This prints three groups: Auto-archivable (will move on --apply), Suggestions
(project entries with a terminal marker or >90d untouched — you decide), and entries
marked resolved but not type: project (left in place by design).
Step 2 — decide. If $ARGUMENTS contains apply (or the user confirms), archive
the auto-archivable set:
bash ${CLAUDE_PLUGIN_ROOT}/tools/memory-prune.sh --apply
For an entry in the Suggestions list that the user confirms is done, don't force it —
edit that entry's frontmatter to add status: resolved under metadata:, then re-run
--apply. That keeps the author-declared safety model intact.
Other actions:
bash ${CLAUDE_PLUGIN_ROOT}/tools/memory-prune.sh --list-archive— show archived entries.bash ${CLAUDE_PLUGIN_ROOT}/tools/memory-prune.sh --restore <name>— bring one back (re-adds its index line).
Report the tool output verbatim, then state how many entries were archived (or would be) and the approximate per-session token saving (each index line ≈ 40–60 tokens).
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.
- 8d ago First seen · 37 lines · 0 tokens per session scan A 3d17ca6325aa
memory-prune is a command published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 448 tokens. 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.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.