Ext Ops Panel
Open dashboard
Comparison

jpyc-dev-reference vs rayfin

jpyc-dev-reference is a plugin bundle for AI coding tools published by Mameta29. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). rayfin is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). 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
Marketplacejpyc-dev-referencerayfin
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.4.2
Forks (GitHub): 69
Stars (GitHub): 639
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

jpyc-dev-reference vs rayfin
Factjpyc-dev-referencerayfin
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)639 (better)
Forks (GitHub) (differs)0 (worse)69 (better)
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
Parts of the bundle11
Licence (differs)Not statedMIT
Repository (differs)github.com/mameta29/jpyc-skillgithub.com/microsoft/rayfin
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

jpyc-dev-reference

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

Developer reference for JPYC, a JPY-pegged stablecoin (日本円ステーブルコイン) deployed on Ethereum, Polygon, and Avalanche. Provides contract addresses, ERC20 functions, EIP-3009 gasless transfer signatures, EIP-2612 permit, admin/role operations (mint, burn, pause, blocklist), EIP712 domain configuration, type hashes, error messages, and TypeScript/viem code examples.

rayfin

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

Getting-started router skill for Rayfin - scaffold a new app with the Rayfin CLI, then use the version-locked skill installed in the project.

How to run each

jpyc-dev-reference

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

rayfin

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

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: jpyc-dev-reference · What it can do: rayfin · 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 the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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