Agent Memory Curator Agent — Development skill for Claude Code
Memory Curator Agent for scoped memory governance in multi-agent workflows.
How to install Agent Memory Curator Agent
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open agentlas-ai/agent_memory_curator_agent and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Agent Memory Curator Agent does
Memory Curator Agent for scoped memory governance in multi-agent workflows.
Alternatives in Development
- Enterprise Policy — Enterprise Skill Governance 720 ★
- Claude Cognitive — Working memory for Claude Code - persistent context and multi-instance coordination 440 ★
- Maintainer — Meta-skill that loads all llmwiki governance docs and exposes the three maintainer slash commands 375 ★
README
Self-Evolving Agents Hallucinate at Scale: A Provable Memory Curator Architecture
**Mason Lee** Appbridge Inc. (Agentlas) [agentlas.cloud](https://agentlas.cloud) · appbridge@appbridge.co.kr
**Version:** v2.0 preprint draft (May 26, 2026) **Code:** [github.com/agentlas-ai/agent_memory_curator_agent](https://github.com/agentlas-ai/agent_memory_curator_agent) **License:** MIT (code), CC-BY 4.0 (paper)
Abstract
**We prove that self-evolving LLM agents — Hermes, Voyager-style skill libraries, and their production kin — accumulate retrieval hallucinations at a rate that approaches certainty as deployment horizons grow, unless durable memory writes are explicitly governed.** Monte Carlo simulation over 200 seeds confirms the bound: an uncurated self-evolving agent operating at 10 events/day with realistic 10% per-event hallucination probability reaches a **98.6% per-retrieval hallucination probability** within one year. A curator with admission rate $\alpha = 0.3$ and filter accuracy $\eta = 0.9$ cuts this to **30.7%** — a 3.2× reduction. A stricter curator ($\alpha = 0.5$, $\eta = 0.95$) cuts it to **17.7%** — a 5.6× reduction.
We formalize the *memory admission problem* in multi-agent settings and prove a *compounding-bound theorem*: under mild assumptions, the per-retrieval hallucination probability in an uncurated regime grows asymptotically as $1 - (\lambda t)^{-r_0 h_e}$, whereas a curator bounds the rate at $1 - (\alpha \lambda t)^{-r_0 h_e (1-\eta)}$, with the ratio diverging to infinity as $t \to \infty$ for any $\eta > 0$.
The bound motivates a system design. We propose the **Memory Curator Agent**: a dedicated specialist that owns durable memory writes while worker agents emit *structured memory events*. Memory is partitioned into four scopes — *agent repo*, *agent team*, *project*, *session* — corresponding to specialist, transacti
Related Skills
Memory Tidy
You are a memory curator for Omux. Your job is to review a single memory file and decide which entries to keep
Obsidian Curator
The 4th layer of the Claude+Obsidian memory stack — deterministic knowledge-graph maintenance (rename/link/pru
Tech Debt
Multi-agent technical-debt assessment — fans out region-scoped + specialist hunters, verifies findings, scores
Cc Council
Comprehensive multi-agent council review with 6 protocols, 10 specialists, scoped scoring (per-scope threshold
Claude Dev
Autonomous multi-agent development team orchestrator for Claude Code. Team-lead agent dispatches developer/rev
Memory Scratchpad
Read/write plan-scoped shared memory for inter-agent handoff
Related Agents
Gsd Mempalace Curator
Ship-time MemPalace curation — writes the session diary, proposes/creates cross-project tunnels, mirrors extra
Specflow Memory Checker
Memory and governance compliance specialist for SpecFlow. Use for constitution, tech-stack, and memory-documen
Governance Learner
Feedback Distiller. Use this agent at sprint close to audit /memory/ logs, distill systemic patterns from bug-