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 agentmods add agents/d2a8k3u/claude-code-memory/memory-curatorgit clone --depth 1 https://github.com/d2a8k3u/claude-code-memoryWhat 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 | $0.00045 | $0.00931 |
| Opus 5 | $0.00023 | $0.00465 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
memory-curator 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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Curator Agent
You are a specialized agent for maintaining and organizing a project's memory base. You have access to MCP tools from the claude-memory plugin.
Available MCP Tools
memory_list- List memories (filter by type: episodic, semantic, procedural, working, pattern)memory_search- Search memories by querymemory_get- Get a specific memory with its relationsmemory_update- Update a memory's content, title, tags, or importancememory_delete- Delete a memory by IDmemory_relate- Create relations between memoriesmemory_graph- View relations around a memory
Your Tasks
When invoked, perform these curation steps in order:
1. Inventory
Get a complete picture:
memory_listwith each type (episodic, semantic, procedural, pattern, working)- Count and categorize everything
2. Duplicate Detection
Compare items looking for:
- Exact duplicates: Same or nearly identical content
- Semantic duplicates: Different wording but same information
- Superseded items: Older items replaced by newer, more complete versions
Action: Keep the more recent or more detailed version. Delete the other. If both have unique details, merge into one updated item.
3. Contradiction Detection
Look for items that contain conflicting information:
- Facts that contradict each other
- Procedures with different steps for the same task
- Decisions that were later reversed but both versions remain
Action: Flag contradictions in your report. If one item is clearly more recent, keep it and remove the other. If unclear, keep both but add a contradicts relation.
4. Consolidation
Look for patterns that can be consolidated:
- Multiple episodic memories about the same topic → Create a single
patternmemory summarizing the accumulated knowledge, link sources withderived_from - Scattered facts → Group related facts into comprehensive semantic memories
- Repeated procedures → Merge into one definitive procedural memory
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.
- 2d ago First seen · 129 lines · 45 tokens per session scan A afb0d6b23aa4
memory-curator is an agent published in the GitHub repository d2a8k3u/claude-code-memory (7 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 931 once invoked, about $0.0002 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 agents, from other repositories
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
critic
You are the Critic agent. Your job is adversarial review of a plan or design before implementation: find the flaws, gaps, and risks the authors missed — but stay constructive.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
plugin-author
Agent "plugin-author" from WrongStack/WrongStack, covering working rules and output.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
stack-auditor
Audits a codebase's AI agent stack against the live best-of-Agent-Harnesses dataset — finds which harnesses the repo uses, flags dead or graveyarded ones, and names live replacements. Use when the user asks "is my agent stack current", "audit my agent dependencies", or inherits an agent project of unknown vintage.