Ext Ops Panel
Open dashboard
Comparison

pro-workflow vs io.github.keshrath/agent-tasks

pro-workflow is a plugin bundle for AI coding tools published by Rohit Ghumare. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.keshrath/agent-tasks is an MCP server published by keshrath. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-08. 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
Marketplacepro-workflowio.github.keshrath/agent-tasks
Community marketplace rohitg00/pro-workflow Listed
Version: 3.4.0
Forks (GitHub): 299
Stars (GitHub): 2 946
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.0
Downloads/month (npm): 1 307
Downloads/week (npm): 604
Forks (GitHub): 6
Stars (GitHub): 23
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.10.10
Forks (GitHub): 6
Stars (GitHub): 23
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

pro-workflow vs io.github.keshrath/agent-tasks
Factpro-workflowio.github.keshrath/agent-tasks
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 946 (better)23 (worse)
Forks (GitHub) (differs)299 (better)6 (worse)
Last release (differs)Not published2026-10-24
Where it runs (differs)Installs as a plugin bundleOn your machine (agent-tasks)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 7Not published
Hooks it runs (differs)35Not published
Parts of the bundle (differs)1071
LicenceMITMIT
Repository (differs)github.com/rohitg00/pro-workflowgithub.com/keshrath/agent-tasks
Changes in the last 7 days22
First seen (differs)2026-11-042026-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

pro-workflow

In its own words, on Community GitHub marketplaces:

Complete AI coding workflow: context engineering, agent teams, 41 skills, 8 agents, 23 commands, 13 guides, cross-agent support, and searchable learnings.

io.github.keshrath/agent-tasks

In its own words, on Official MCP Registry:

Pipeline task management for AI agents - stages, dependencies, artifacts, claiming

How to run each

pro-workflow As a Claude Code plugin

Claude Code
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

io.github.keshrath/agent-tasks As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-tasks -- npx -y agent-tasks

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

The marketplaces of io.github.keshrath/agent-tasks publish no settings it asks for, so we do not compare settings.

What it can do: pro-workflow · What it can do: io.github.keshrath/agent-tasks · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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