Ext Ops Panel
Open dashboard
Comparison

cache-stats vs jelly-pet

cache-stats is a plugin bundle for AI coding tools published by arafattehsin. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). jelly-pet is a plugin bundle for AI coding tools published by ejlee-0924. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-23. 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
Marketplacecache-statsjelly-pet
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 06c89b8
No figure published
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

cache-stats vs jelly-pet
Factcache-statsjelly-pet
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-14Not 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
Licence (differs)MITNot stated
Repository (differs)github.com/arafattehsin/cache-stats-extensiongithub.com/ejlee-0924/jelly-pet
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

cache-stats

In its own words, on Copilot CLI: github/awesome-copilot:

Shows live prompt-cache reuse, expiry, token composition, and AI Credit cost for the current GitHub Copilot session without making model calls.

jelly-pet

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

Jelly Pet turns your Claude Code sessions into a pet-raising game. Every time you code, your output tokens are converted into "jelly" — and your pet eats jelly to grow and evolve. Choose from 5 species (cat, dog, hamster, rabbit, hedgehog), name your pet, and watch it evolve from Egg to Legend across 5 stages. A multi-line ASCII pet lives in your statusline, greets you at session start, and reports your jelly earnings at session end. Daily streak bonuses (up to 2x) reward consistent usage. All data stays local — zero external dependencies, zero network calls.

How to run each

cache-stats

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

jelly-pet As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install jelly-pet@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: cache-stats · What it can do: jelly-pet · Compare two other plugins

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