Ext Ops Panel
Open dashboard
Comparison

rayfin vs spree-commerce

rayfin is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). spree-commerce is a plugin bundle for AI coding tools published by Rohit Bajaj, Julekha Khatun. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplacerayfinspree-commerce
Copilot CLI: github/awesome-copilot Listed
Version: 0.4.2
Forks (GitHub): 70
Stars (GitHub): 640
Not marked · First seen
Not listed
Community marketplace orcaqubits/agentic-commerce-claude-plugins Not listed Listed
Version: 1.0.0
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

rayfin vs spree-commerce
Factrayfinspree-commerce
Marketplaces that list it11
Stars (GitHub) (differs)640No figure on GitHub
Forks (GitHub) (differs)70No figure on GitHub
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)Not published2
Parts of the bundle (differs)125
LicenceMITMIT
Repository (differs)github.com/microsoft/rayfingithub.com/orcaqubits/agentic-commerce-claude-plugins
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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

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.

spree-commerce

In its own words, on Community GitHub marketplaces:

Spree Commerce — open-source Rails e-commerce platform (BSD-3, since 2007, v5+) with consolidated `spree` umbrella gem, Tailwind/Hotwire Admin Dashboard, API v3 (flat JSON + OpenAPI 3.0) + legacy API v2, the @spree/sdk TypeScript SDK, Order/Payment/Shipment state machines, prepend-based decorators, Spree::Events bus + Webhooks 2.0, Promotions engine, Payment Sessions (Stripe/Adyen/PayPal), Multi-store + Markets + Marketplace, Next.js headless storefront, RSpec + spree_dev_tools, and PostgreSQL/Redis/Sidekiq/Docker deployment

How to run each

rayfin

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

spree-commerce As a Claude Code plugin

Claude Code
/plugin marketplace add orcaqubits/agentic-commerce-claude-plugins
/plugin install spree-commerce@agentic-commerce

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: rayfin · What it can do: spree-commerce · 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 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