Ext Ops Panel
Open dashboard
Comparison

microsoft-foundry vs nxtg-forge

microsoft-foundry is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). nxtg-forge is a plugin bundle for AI coding tools published by nxtg-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-18. 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
Marketplacemicrosoft-foundrynxtg-forge
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.14
Forks (GitHub): 262
Stars (GitHub): 2 056
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.10.4
Forks (GitHub): 2
Stars (GitHub): 6
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

microsoft-foundry vs nxtg-forge
Factmicrosoft-foundrynxtg-forge
Marketplaces that list it11
Stars (GitHub) (differs)2 056 (better)6 (worse)
Forks (GitHub) (differs)262 (better)2 (worse)
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
LicenceMITMIT
Repository (differs)github.com/microsoft/foundry-dev-toolsgithub.com/nxtg-ai/forge-plugin
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

microsoft-foundry

In its own words, on Copilot CLI: github/awesome-copilot:

Skills and interactive Copilot canvas for designing, configuring, testing and deploying agents to Microsoft Foundry.

nxtg-forge

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

Structural governance for AI coding agents. 33 agents, 23 commands, 32 skills, 8 MCP governance tools, and 7 hooks that enforce a core rule: verifier.agent != task.agent — no agent grades its own homework. Adds health scoring (A-F grades across 8 dimensions), live drift detection, quality gates, cross-agent verification, and shared memory to any Claude Code project. Optional Rust orchestrator (4MB binary) for file locking and multi-tool coordination across Claude Code, Codex CLI, and Gemini CLI. 4,579 tests across the trilogy. Built from 23 years of global program delivery. MIT licensed.

How to run each

microsoft-foundry

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

nxtg-forge As a Claude Code plugin

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

Neither one's marketplaces publish the settings it asks for.

What it can do: microsoft-foundry · What it can do: nxtg-forge · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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