Borrowing it
Nothing to install: this file belongs to theshadow27/mcp-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theshadow27/mcp-cli/main/.claude/skills/memory-gc/SKILL.mdgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/skills/theshadow27/mcp-cli/memory-gc)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/memory-gc"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/memory-gc/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/skills/theshadow27/mcp-cli/memory-gc"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/memory-gc.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.00091 | $0.01549 |
| Opus 5.5 | $0.00036 | $0.00620 |
| Sonnet 5.5 | $0.00018 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
memory-gc 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memory-gc — garbage-collect committed memory
On this project the "user-local" memory store is committed to the repo — it is shared team context, not a private scratchpad. That means it rots like any doc: facts duplicate CLAUDE.md, reference closed issues, describe subsystems that moved, or accrete sprint mechanics that belong in the sprint skill. This skill audits every memory with evidence, then applies only the safe changes.
Canonical store path (symlinked from ~/.claude/projects/<slug>/memory/):
<repo>/.claude/memory/ — MEMORY.md is the index (one line per memory); each line links a
per-fact *.md file. Some facts live inline in MEMORY.md with no backing file.
Why a workflow (don't do this single-threaded)
The highest-value verdict — "this is OBE, delete it" — is also the easiest to get wrong by guessing.
Every memory that references an issue/PR/commit/flag must be verified against live state (gh,
git, codebase grep) before it can be called outdated. That is dozens of independent gh calls;
fan them out to one sonnet worker per memory so each gathers its own evidence in its own context.
The orchestrator only ever sees the conclusions.
Method (4 steps)
1. Inventory + integrity (bidirectional)
cd <repo>/.claude/memory
# files not indexed in MEMORY.md (orphans):
for f in *.md; do [ "$f" = MEMORY.md ] && continue; grep -q "($f)" MEMORY.md || echo "ORPHAN: $f"; done
# index lines whose file is gone (broken links):
grep -oE '\]\([a-z0-9_-]+\.md\)' MEMORY.md | sed -E 's/\]\(|\)//g' | while read l; do [ -f "$l" ] || echo "MISSING: $l"; done
Also enumerate the inline facts (MEMORY.md lines with no link) — group them by section; they get
audited too. Enumerate the comparison targets that actually exist: the project CLAUDE.md, any
package/dir CLAUDE.md (test/, packages/*/), and the sprint skill (SKILL.md + references/*).
Do not compare against a parent repo's CLAUDE.md — that's a different repo's concern.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 96 lines · 91 tokens per session scan A f457fe71e497
memory-gc is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 3d ago), licensed MIT. It adds 91 tokens to every session and 1,549 once invoked, about $0.0004 per session on Opus 5.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.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.