gather vs pmm
gather is a plugin bundle for AI coding tools published by hunta.ai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). pmm is a plugin bundle for AI coding tools published by NominexHQ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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
| Marketplace | ||
|---|---|---|
| Community marketplace hunta-ai/gather | Not seen in the last pass Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 2.7.0 Forks (GitHub): 8 Stars (GitHub): 15 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
| Fact | gather | pmm |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 15 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 8 (better) |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 4 | 2 |
| Parts of the bundle (differs) | 6 | 14 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/hunta-ai/gather | github.com/nominexhq/pmm-plugin |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-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
gather
Deterministic org-memory for Claude Code: auto-recall on every prompt (fail-open), re-inject after compaction, loss-proof capture to Gather's curated staging inbox. Nothing enters canon without promotion.
pmm
If you have ever had AI hallucinate and make things up (and gaslight you, even): it's because summaries do not preserve nuance. Each /compact cycle summarises and compresses. Decisions lose their rationale. Lessons lose their context. By Monday, you're re-explaining choices you made on Thursday. That's context rot. PMM fixes that. Every session, Claude loads what it already knows, then adds to it. Markdown files, git-backed. No database, no setup. Decisions tracked with rationale: not just what but. git log as your memory audit trail. Memory that compounds, not rots.
How to run each
gather As a Claude Code plugin
/plugin marketplace add hunta-ai/gather
/plugin install gather@hunta
pmm As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pmm@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: gather · What it can do: pmm · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.