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.
npx skills add cveralyon/axel-setup --skill memory-reviewgit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/memory-review)<a href="https://agentmods.dev/skills/cveralyon/axel-setup/memory-review"><img src="https://agentmods.dev/badge/skills/cveralyon/axel-setup/memory-review.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.00061 | $0.00844 |
| Opus 5 | $0.00030 | $0.00422 |
| Sonnet 5 | $0.00012 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
memory-review 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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Review & Optimization
Interactive memory maintenance skill. When invoked, systematically reviews all memory files and works with the user to keep the memory system clean, relevant, and efficient.
Workflow
Phase 1: Audit
- Read
~/.claude/memory/MEMORY.md(index) - Read every memory file listed in the index
- Detect any orphan files (exist on disk but not in index)
- For each memory file, evaluate:
- Staleness: Does the content reference things that may have changed? (team members, tools, architectures)
- Redundancy: Is this duplicated or overlapping with another memory file?
- Relevance: Is this still useful for future conversations?
- Accuracy: Does this match current reality? (verify against code/git if needed)
- Size: Is this too verbose? Can it be trimmed without losing value?
Phase 2: Report
Present a structured report to the user:
## Memory Audit Report
### Summary
- Total files: X
- Index entries: X
- Orphan files: X (not in index)
- Potentially stale: X
- Candidates for merge: X
- Candidates for removal: X
### Per-File Analysis
For each file, show:
- Status: OK / STALE / MERGE_CANDIDATE / REMOVE_CANDIDATE
- Last modified: date
- Reason: why this status
- Suggested action: keep / update / merge with X / remove
Phase 3: Interactive Q&A
Ask the user targeted questions to resolve ambiguities:
- "Is X still accurate?"
- "Should I merge A and B since they overlap?"
- "This mentions Y which seems outdated — remove or update?"
- "Any new context I should add?"
Keep questions grouped and numbered for easy answering. Max 5-7 questions per round.
Phase 4: Execute
Based on user answers:
- Update stale files with correct information
- Merge redundant files
- Remove files the user confirms as unnecessary
- Add any new memory files the user requests
- Rebuild
MEMORY.mdindex with accurate one-line descriptions - Sync both memory locations:
~/.claude/memory/(shared, primary)~/.claude/projects/(legacy fallback, path varies by user)
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.
- 7d ago First seen · 101 lines · 61 tokens per session scan A f1ee7ea37d47
memory-review is a skill published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 844 once invoked, about $0.0003 per session on Opus 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
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.
continuous-learning-v2
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
codebase-memory-mcp
Resolve canonical Git checkouts, index and verify codebase-memory-mcp graphs through the guarded CLI, and safely audit duplicate worktree caches. Use when a user mentions codebase memory MCP, searchgraph, tracepath, indexrepository, worktree indexes, or oversized graph caches.
project-memory
Initialize, retrieve, and explicitly update the separate Rootloom Memory plugin's repository-owned architecture, risk, decision, and failure lessons. Use only when explicitly requested. Memory is experimental, advisory, and outside Rootloom Core.
memory-hygiene
Keep agent-written memory files from rotting. Audits /.claude/projects/ /memory/ for facts the tree now contradicts — stale version pins, passed sequence facts, vanished paths — plus MEMORY.md index drift, and enforces the memory format contract at write time. Use when the user says "audit my memory", "memory is…
learn-on-failure
Save a learning to project memory. Invoke automatically (without the user asking) whenever a task required more than one fix cycle to resolve — e.g. a test failed and needed a second attempt, a compile error required a correction, an API behaved unexpectedly, or an assumption proved wrong mid-task. Also invoke when…