Ext Ops Panel
Open dashboard
Comparison

memory-toolkit vs wikimoth

memory-toolkit is a plugin bundle for AI coding tools published by IlyaGorsky. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). wikimoth is a plugin bundle for AI coding tools published by Julian Geymonat. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacememory-toolkitwikimoth
Claude Code: claude-plugins-community Listed
Version: 1.9.12
Forks (GitHub): 2
Stars (GitHub): 13
Not marked · First seen
Not listed
Community marketplace juliangeymonat-jpg/wikimoth Not listed Listed
Version: 0.2.3
Forks (GitHub): 0
Stars (GitHub): 8
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

memory-toolkit vs wikimoth
Factmemory-toolkitwikimoth
Marketplaces that list it11
Stars (GitHub) (differs)13 (better)8 (worse)
Forks (GitHub) (differs)2 (better)0 (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)65
Parts of the bundle (differs)165
Licence (differs)MITApache-2.0
Repository (differs)github.com/ilyagorsky/memory-toolkitgithub.com/juliangeymonat-jpg/wikimoth
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-13

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

memory-toolkit

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

Session memory lifecycle for Claude Code. Structured handoffs between sessions, workstreams to switch context without losing it, background watcher (Haiku) that captures decisions and corrections in real time, docs pipeline that routes session findings into .claude/rules/, model recommendations per task, and PreCompact hook to survive context compaction. Works alongside CLAUDE.md and auto-memory — no daemon, no vector DB, no external dependencies. MIT licensed.

wikimoth

In its own words, on Community GitHub marketplaces:

Deterministic, token-minimal memory for Claude Code: capture each session as a [[wikilink]] note (edges computed by code, not a model) and recall connected notes at boot.

How to run each

memory-toolkit As a Claude Code plugin

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

wikimoth As a Claude Code plugin

Claude Code
/plugin marketplace add juliangeymonat-jpg/wikimoth
/plugin install wikimoth@juliangeymonat-jpg

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: memory-toolkit · What it can do: wikimoth · Compare two other plugins

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