Ext Ops Panel
Open dashboard
Comparison

memstack vs learned-behavior

memstack is a plugin bundle for AI coding tools published by cwinvestments. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). learned-behavior is a plugin bundle for AI coding tools published by lisn0. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
Marketplacememstacklearned-behavior
Claude Code: claude-plugins-community Listed
Version: 3.7.0
Forks (GitHub): 45
Stars (GitHub): 425
Not marked · First seen
Listed
Version: 0.2.0
Forks (GitHub): 1
Stars (GitHub): 0
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

memstack vs learned-behavior
Factmemstacklearned-behavior
Marketplaces that list it11
Stars (GitHub) (differs)425 (better)0 (worse)
Forks (GitHub) (differs)45 (better)1 (worse)
Last releaseNot publishedNot 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)17
Parts of the bundle (differs)198
LicenceMITMIT
Repository (differs)github.com/cwinvestments/memstackgithub.com/lisn0/learned-behavior
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

memstack

In its own words, on Claude Code: claude-plugins-community:

100 battle-tested skills for Claude Code across 10 categories: session memory, git workflows, database migrations, security scanning, deployments, API development, frontend, content/marketing, business docs, and DevOps. Auto-trigger commands fire based on what you're working on. Session handoffs preserve context across conversations. One install deploys across all your projects. 77 free skills included, 23 Pro-exclusive available at memstack.pro.

learned-behavior

In its own words, on Claude Code: claude-plugins-community:

Self-improving memory for Claude Code. Observes hooks (tool use, edits, errors, guard blocks), distills recurring patterns into durable rules, and surfaces relevant approved lessons before each task. No LLM in the loop, no self-report, purely behavioral. Local SQLite, zero dependencies, no telemetry.

How to run each

memstack As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install memstack@claude-community

learned-behavior As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install learned-behavior@claude-community

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: memstack · What it can do: learned-behavior · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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