Ext Ops Panel
Open dashboard
Comparison

mirror vs hyperflow

mirror is a plugin bundle for AI coding tools published by Furkan Aydın. Marketplaces we read that list it: 1 (Community GitHub marketplaces). hyperflow is a plugin bundle for AI coding tools published by Mohammed-Abdelhady. 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

Where each is published
Marketplacemirrorhyperflow
Community marketplace aydinfurkan/mirror Not seen in the last pass
Version: 0.5.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 6.1.0
Forks (GitHub): 0
Stars (GitHub): 3
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

mirror vs hyperflow
Factmirrorhyperflow
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
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)1Not published
Parts of the bundle (differs)514
LicenceMITMIT
Repository (differs)github.com/aydinfurkan/mirrorgithub.com/mohammed-abdelhady/hyperflow
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-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

mirror

In its own words, on Community GitHub marketplaces:

A mirror of your code: a living map of every flow and page. Claude updates the mirror first, you approve, then the code follows.

hyperflow

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

Hyperflow turns a Claude Code session into a structured engineering workflow through eight chained slash commands. /hyperflow:spec runs a guided design session with structured questions and section-by-section approval. /hyperflow:scope decomposes the design into a batched task file. /hyperflow:dispatch runs parallel persona-stitched workers under thinking-tier review at every step. Multi-level code review (L1–L5), 15 composable personas covering security, frontend, backend, database, and more, six adaptive flow profiles tuned to task complexity. Project memory persists across sessions so context, decisions, and learned conventions carry forward.

How to run each

mirror As a Claude Code plugin

Claude Code
/plugin marketplace add aydinfurkan/mirror
/plugin install mirror@mirror

hyperflow As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install hyperflow@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: mirror · What it can do: hyperflow · 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.

Where the data comes from: how the catalog is built