Ext Ops Panel
Open dashboard
Comparison

sourcery-agent vs codixing

sourcery-agent is a plugin bundle for AI coding tools published by abyssbugg. Marketplaces we read that list it: 1 (Community GitHub marketplaces). codixing is a plugin bundle for AI coding tools published by ferax564. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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
Marketplacesourcery-agentcodixing
Community marketplace abyssbugg-labs/sourcery-agent-bundle Listed
Version: 0.2.4
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.48.0
Forks (GitHub): 0
Stars (GitHub): 2
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

sourcery-agent vs codixing
Factsourcery-agentcodixing
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@abyssbugg/sourcery)On your machine (codixing-mcp)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)48
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/abyssbugg-labs/sourcery-agent-bundlegithub.com/ferax564/codixing
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-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

sourcery-agent

In its own words, on Community GitHub marketplaces:

Sourcery security findings for AI coding agents: triage and minimal-change remediation via the public Sourcery API (12 MCP tools + skills).

codixing

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

Code retrieval engine that gives Claude structural understanding of your codebase. Before modifying code, Codixing tells Claude what will break, predicting impact across the dependency graph, finding affected tests, and tracing callers through the call hierarchy. Unlike text search, Codixing builds an AST-aware index with BM25 + semantic hybrid retrieval, dependency graphs with PageRank ranking, and trigram-accelerated grep; all running locally with zero cloud dependencies.

How to run each

sourcery-agent As a Codex plugin

Codex
codex plugin marketplace add abyssbugg-labs/sourcery-agent-bundle

codixing As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install codixing@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

The marketplaces of codixing publish no settings it asks for, so we do not compare settings.

What it can do: sourcery-agent · What it can do: codixing · 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