Ext Ops Panel
Open dashboard
Comparison

cxpak vs io.github.Digital-Threads/token-pilot

cxpak is a plugin bundle for AI coding tools published by Barnett-Studios. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Digital-Threads/token-pilot is an MCP server published by Digital-Threads. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
Marketplacecxpakio.github.Digital-Threads/token-pilot
Claude Code: claude-plugins-community Listed
Version: 3.1.3
Forks (GitHub): 2
Stars (GitHub): 31
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
Downloads/month (npm): 3 108
Downloads/week (npm): 296
Forks (GitHub): 2
Stars (GitHub): 5
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

cxpak vs io.github.Digital-Threads/token-pilot
Factcxpakio.github.Digital-Threads/token-pilot
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)31 (better)5 (worse)
Forks (GitHub)22
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (token-pilot)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published13
Parts of the bundle (differs)834
LicenceMITMIT
Repository (differs)github.com/barnett-studios/cxpakgithub.com/digital-threads/token-pilot
Changes in the last 7 days (differs)02
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

cxpak

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

Token-budgeted codebase context for Claude Code. One call to auto_context gives Claude the optimal context for any task — automatically selecting, ranking, noise-filtering, and packing the most relevant code from your entire codebase. 11 MCP tools including symbol tracing, blast radius analysis, API surface extraction, and semantic search. Supports 42 programming languages via tree-sitter.

io.github.Digital-Threads/token-pilot

In its own words, on Official MCP Registry:

Save up to 80% tokens when AI reads code via AST-aware structural reading

How to run each

cxpak As a Claude Code plugin

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

io.github.Digital-Threads/token-pilot As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio token-pilot -- npx -y token-pilot

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: cxpak · What it can do: io.github.Digital-Threads/token-pilot · 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 Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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