Memory Graveyard
Audit which entries in your project's MEMORY.md Claude actually reads. Use when the user wants to find dead memory entries, broken pointers in MEMORY.md, orphan memory files, or surface entries that fall below the system-prompt truncation cutoff. Triggers on "audit MEMORY.md", "dead memory entries", "broken memory pointers", "memory hygiene", "unused memory", "memory truncation". Runs locally; re…
Install
$ agentstack add skill-sfrangulov-skill-graveyard-memory-graveyard ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sfrangulov-skill-graveyard-memory-graveyard) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
memory-graveyard
CLI that audits per-project file-based memory (MEMORY.md index + memory/*.md entries). Bucketed audit (ACTIVE / DEAD / MISSING / HALLUCINATED) plus a static linter that flags broken pointers, orphan files, truncation-budget overflow, index size, and stale dated entries.
How to invoke
Run via npx memory-graveyard@latest [flags] — no install needed.
Subcommands
audit(default) — 4-bucket per-project table. Flags:--days N,--only,--json,--project,--claude-dir.lint— static checks onMEMORY.mdand the memory dir. Flags:--truncation-cutoff N(default 200),--stale-days N(default 30),--json. Exit 1 on findings.prune— plan removal of dead entries and hallucinated pointers.--applyto execute (with snapshot backup in.graveyard-backup//).--include orphans|broken-pointers,--exclude.projects— cross-project sweep, surfaces cold memory dirs.--cold-days N(default 90).
Decision flow
- "what entries in my MEMORY.md are dead?" →
npx memory-graveyard@latest - "is anything in MEMORY.md broken?" →
npx memory-graveyard@latest lint - "clean up MEMORY.md" →
prune, then--apply - "which projects have stale memory dirs?" →
projects
After running, print output verbatim. Do not summarize unless the user asks.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sfrangulov
- Source: sfrangulov/skill-graveyard
- License: MIT
- Homepage: https://sfrangulov.github.io/skill-graveyard/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.