memory-engineering
v0.1.2Memory engineering team — agents (memory-architect-lead, memory-retention-and-erasure-engineer, memory-eval-cost-analyst) for the decisions behind a durable memory store: what earns a write, which paradigm, which surface holds the bytes, what makes it forget, what a delete leaves behind, cost per correct answer. skills, commands, dated knowledge files, best-practices, templates, scenarios, an advisory hook, a stdlib calculator. Advisory only — it never reads or mutates a real store. Seams: ai-agent-engineering decides whether an agent should remember at all and where state sits in its topology, this engineers the memory system itself; ai-red-teaming owns the ASI06 attack taxonomy and offensive testing, this owns the defensive design half; data-governance-privacy owns DSAR and legal basis, this owns erasure residue in embeddings and version history; retrieval → ai-rag-engineering; evals → llm-evaluation-engineering; the Claude app → claude-app-engineering. Requires ravenclaude-core@>=0.238.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install memory-engineering for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install memory-engineering-2@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/memory-engineering/.
Plugin files
├── .claude-plugin/plugin.json├── skills/budget-memory-costs/SKILL.md├── skills/build-memory-eval/SKILL.md├── skills/choose-memory-paradigm/SKILL.md├── skills/design-forgetting-policy/SKILL.md├── skills/map-memory-surface/SKILL.md└── skills/memory-poisoning-review/SKILL.md
Included Skills6
Put a defensible number on a memory system — break-even against a named baseline, growth and caps, cache-invalidation cost, and cost per correct answer. Reach for this on any pay-for-itself question.
Prove a memory system earns its write path — golden set with provenance, judged failure modes, the runnable bake-off, and cost per correct answer. Reach for this before adopting, replacing or retiring any memory system.
Decide whether to build a memory system at all, and if so which paradigm — raw context, flat retrieval, LLM-extraction or agentic — behind a mandatory baseline-first gate. Reach for this before any memory design work.
Design retention and erasure before the first write — TTL, caps, decay, consolidation timing, dedup, contradiction handling, and what a delete actually leaves behind. Reach for this on any durable store.
Name the storage surface a write actually lands on — who holds the bytes, who executes the write, and what trust model comes with it. Reach for this before writing any memory design down.
Audit an agent's durable memory for poisoning risk and harden it against OWASP ASI06 — enumerate write paths reachable from untrusted input, classify read-only vs read-write, verify audit and rollback. Reach for this when a diff touches a memory store.
Plugin manifests1
{
"name": "memory-engineering",
"version": "0.1.2",
"description": "Memory engineering team — agents (memory-architect-lead, memory-retention-and-erasure-engineer, memory-eval-cost-analyst) for the decisions behind a durable memory store: what earns a write, which paradigm, which surface holds the bytes, what makes it forget, what a delete leaves behind, cost per correct answer. skills, commands, dated knowledge files, best-practices, templates, scenarios, an advisory hook, a stdlib calculator. Advisory only — it never reads or mutates a real store. Seams: ai-agent-engineering decides whether an agent should remember at all and where state sits in its topology, this engineers the memory system itself; ai-red-teaming owns the ASI06 attack taxonomy and offensive testing, this owns the defensive design half; data-governance-privacy owns DSAR and legal basis, this owns erasure residue in embeddings and version history; retrieval → ai-rag-engineering; evals → llm-evaluation-engineering; the Claude app → claude-app-engineering. Requires ravenclaude-core@>=0.238.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"agent-memory",
"memory-store",
"context-engineering",
"retention",
"erasure",
"forgetting-policy",
"memory-poisoning",
"asi06",
"cost-per-correct",
"memory-eval"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.238.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[memory-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/memory-engineering-2)