Ext Ops Panel
Open dashboard
Comparison

claude-code-achievements vs GitHub Inside Claude Code

claude-code-achievements is a plugin bundle for AI coding tools published by subinium. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GitHub Inside Claude Code is an MCP server published by Kirchlive. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceclaude-code-achievementsGitHub Inside Claude Code
Claude Code: claude-plugins-community Listed
Version: 1.3.0
Forks (GitHub): 7
Stars (GitHub): 84
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.6
Downloads/month (PyPI): 109
Downloads/week (PyPI): 37
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

claude-code-achievements vs GitHub Inside Claude Code
Factclaude-code-achievementsGitHub Inside Claude Code
Marketplaces that list it11
Stars (GitHub) (differs)84No figure on GitHub
Forks (GitHub) (differs)7No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (github-inside-claude-code)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 2
Hooks it runs (differs)2Not published
Parts of the bundle (differs)4Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/subinium/claude-code-achievementsgithub.com/kirchlive/github-inside-claude-code
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

claude-code-achievements

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

Steam-style achievement system for Claude Code

GitHub Inside Claude Code

In its own words, on Official MCP Registry:

Normalized GitHub-CLI bridge for Claude Code — 89 ops, 6 families incl. federation sources

How to run each

claude-code-achievements As a Claude Code plugin

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

GitHub Inside Claude Code As a local MCP server: PyPI package

Claude Code
claude mcp add --env "BRAVE_API_KEY=<YOUR_BRAVE_API_KEY>" --env "TAVILY_API_KEY=<YOUR_TAVILY_API_KEY>" --transport stdio github-inside-claude-code -- uvx gh-tool-use-mcp github-inside-claude-code

Requires: BRAVE_API_KEY (secret), TAVILY_API_KEY (secret)

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 claude-code-achievements publish no settings it asks for, so we do not compare settings.

What it can do: claude-code-achievements · What it can do: GitHub Inside Claude Code · 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. 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