Ext Ops Panel
Open dashboard
Comparison

agnix vs Cursor Team Kit

agnix is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Cursor Team Kit is a plugin bundle for AI coding tools published by Eric Zakariasson. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). As of our marketplace pass on 2026-10-13. 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
MarketplaceagnixCursor Team Kit
Claude Code: claude-plugins-community Listed
Version: c9e4761
Forks (GitHub): 34
Stars (GitHub): 449
Not marked · First seen
Not listed
Cursor: cursor/plugins Not listed Listed
Version: 1.2.0
Forks (GitHub): 1 086
Stars (GitHub): 11 186
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

agnix vs Cursor Team Kit
FactagnixCursor Team Kit
Marketplaces that list it11
Stars (GitHub) (differs)449 (worse)11 186 (better)
Forks (GitHub) (differs)34 (worse)1 086 (better)
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
Parts of the bundle (differs)122
Licence (differs)Not statedMIT
Repository (differs)github.com/agent-sh/agnixgithub.com/cursor/plugins
Changes in the last 7 days00
First seen2026-10-112026-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

agnix

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

Lint agent configurations before they silently fail. 414 validation rules across Claude Code, Codex CLI, OpenCode, Cursor, GitHub Copilot, Gemini CLI, Cline, Windsurf, Roo Code, Amp, and Kiro - validates CLAUDE.md, AGENTS.md, SKILL.md, hooks.json, MCP server configs, and plugin manifests. Auto-fix included for safe issues; SARIF output for GitHub Code Scanning. Distributed as CLI (npm + Cargo), official GitHub Action (`agent-sh/agnix`), and IDE extensions for VS Code, JetBrains, Neovim, and Zed. Rules sourced from official specs, academic research on agent prompt design, and real-world failure patterns from production deployments. Mentioned in awesome-claude-code.

Cursor Team Kit

In its own words, on Cursor: cursor/plugins:

Internal team workflows for CI, code review, shipping, local automation, and verification.

How to run each

agnix As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agnix@claude-community

Cursor Team Kit

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

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: agnix · What it can do: Cursor Team Kit · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-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