Ext Ops Panel
Open dashboard
Comparison

agent-memory vs Memory

agent-memory is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Memory is a plugin bundle for AI coding tools published by Frad LEE. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceagent-memoryMemory
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.1
Forks (GitHub): 3 987
Stars (GitHub): 28 744
Not marked · First seen
Not listed
Community marketplace fradser/dotclaude Not listed Listed
Version: 0.1.5
Forks (GitHub): 51
Stars (GitHub): 596
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

agent-memory vs Memory
Factagent-memoryMemory
Marketplaces that list it11
Stars (GitHub) (differs)28 744 (better)596 (worse)
Forks (GitHub) (differs)3 987 (better)51 (worse)
Last release (differs)2026-10-23Not published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)62
LicenceMITMIT
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/fradser/dotclaude
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-18

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

agent-memory

In its own words, on Community GitHub marketplaces:

A four-tier memory ladder for Claude Code where promotion is earned by recurrence, not asserted by confidence. L0 raw transcripts are never injected; L1 candidate atoms are gitignored and recalled on lexical relevance per prompt; L2 project context loads each session start; L3 stable persona is always loaded. L1 to L2 needs three distinct sessions spanning two distinct calendar days (a stated claim needs two; a verified claim is the only single-observation path); L2 to L3 needs two projects and thirty days. Two gates refuse rather than guess: a claim altered by the redaction pass never promotes on evidence alone, and a contradicted claim freezes until a human resolves it. Three hooks run the loop unattended and every one fails open. Nothing reaches a committed CLAUDE.md without an explicit human adopt. Ships 5 stdlib scripts, 3 hooks, a cs-memory-curator agent, /cs-memory, a JSON schema, and a 69-check validator. Concept from TencentCloud/TencentDB-Agent-Memory (MIT); no upstream code included.

Memory

In its own words, on Community GitHub marketplaces:

Active memory writing during conversation, plus manual /memory:consolidate with theme clustering, ground-truth prune, adversarial pass, and machine validator — no auto-consolidation

How to run each

agent-memory As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install agent-memory@claude-code-skills

Memory As a Claude Code plugin

Claude Code
/plugin marketplace add fradser/dotclaude
/plugin install memory@frad-dotclaude

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: agent-memory · What it can do: Memory · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built