Ext Ops Panel
Open dashboard
Comparison

webcmd vs zyte-web-data

webcmd is a plugin bundle for AI coding tools published by AgentRHQ. Marketplaces we read that list it: 1 (Community GitHub marketplaces). zyte-web-data is a plugin bundle for AI coding tools published by zytedata. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacewebcmdzyte-web-data
Community marketplace agentrhq/webcmd Listed
Version: 0.8.4
Forks (GitHub): 1 544
Stars (GitHub): 2 713
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 0.3.1
Forks (GitHub): 5
Stars (GitHub): 33
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.3
Forks (GitHub): 5
Stars (GitHub): 33
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

webcmd vs zyte-web-data
Factwebcmdzyte-web-data
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)2 713 (better)33 (worse)
Forks (GitHub) (differs)1 544 (better)5 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.zyte.com/v1/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)115
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/agentrhq/webcmdgithub.com/zytedata/claude-skills
Changes in the last 7 days22
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

webcmd

In its own words, on Community GitHub marketplaces:

Webcmd browser skill for live, authenticated browser automation with local sitemap memory. Requires the @agentrhq/webcmd npm CLI.

zyte-web-data

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

Web scraping skills for Claude Code powered by the Zyte API — scrape sites, generate and run Scrapy spiders, define extraction schemas, and ship to Scrapy Cloud.

How to run each

webcmd As a Claude Code plugin

Claude Code
/plugin marketplace add agentrhq/webcmd
/plugin install webcmd@webcmd

zyte-web-data As a Claude Code plugin

Claude Code
/plugin install zyte-web-data@claude-plugins-official

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: webcmd · What it can do: zyte-web-data · 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-official/blob/HEAD/.claude-plugin/marketplace.json. 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