Ext Ops Panel
Open dashboard
Comparison

handoff-engineering vs mexus-agent-team

handoff-engineering is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). mexus-agent-team is a plugin bundle for AI coding tools published by yofine. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-29. 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
Marketplacehandoff-engineeringmexus-agent-team
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.2
Forks (GitHub): 4 016
Stars (GitHub): 28 939
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 11
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

handoff-engineering vs mexus-agent-team
Facthandoff-engineeringmexus-agent-team
Marketplaces that list it11
Stars (GitHub) (differs)28 939 (better)11 (worse)
Forks (GitHub) (differs)4 016 (better)0 (worse)
Last release (differs)2026-10-26Not 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 bundle (differs)35
Licence (differs)MITNot stated
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/yofine/mexus-agent-team
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

handoff-engineering

In its own words, on Community GitHub marketplaces:

Conversation-handoff document generator. Compacts the current session into a markdown handoff for a fresh agent — references existing artifacts (PRDs, plans, ADRs, issues, commits) by path/URL instead of duplicating them. Derived from Matt Pocock's MIT-licensed handoff with: (1) 3 stdlib Python tools (template generator tailored to 5 next-session emphases, artifact deduplicator across 5 categories of duplication, skill recommender matching content to 14 skills in this repo), (2) 4 references citing 7-8 sources (handoff structure, deduplication discipline, next-session skill matching, companion tooling), (3) cs-handoff-author persona agent + /cs-handoff slash command. Matt's no-duplication discipline + mktemp convention preserved verbatim per MIT.

mexus-agent-team

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

Standalone Markdown-only Agent Team plugin for Claude Code and Codex. Coordination happens through ordinary Markdown files in the current project: agent-team/ ├── mission-workflow.md ├── agents.md └── missions/<mission-name>/ ├── mission.md ├── agents.md ├── kanban.md ├── roundtable.md └── squad-lead.md

How to run each

handoff-engineering As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install handoff-engineering@claude-code-skills

mexus-agent-team As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mexus-agent-team@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: handoff-engineering · What it can do: mexus-agent-team · 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