Ext Ops Panel
Open dashboard
Comparison

module-gates vs project-boundary

module-gates is a plugin bundle for AI coding tools published by Cause Chung. Marketplaces we read that list it: 1 (Community GitHub marketplaces). project-boundary is a plugin bundle for AI coding tools published by justi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-23. 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
Marketplacemodule-gatesproject-boundary
Community marketplace cuzfrog/module-gates Listed
Version: 0.22.0
Forks (GitHub): 0
Stars (GitHub): 56
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.11.0
Forks (GitHub): 3
Stars (GitHub): 90
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

module-gates vs project-boundary
Factmodule-gatesproject-boundary
Marketplaces that list it11
Stars (GitHub) (differs)56 (worse)90 (better)
Forks (GitHub) (differs)0 (worse)3 (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
Hooks it runs (differs)25
Parts of the bundle (differs)32
Licence (differs)Not statedMIT
Repository (differs)github.com/cuzfrog/module-gatesgithub.com/justi/claude-code-project-boundary
Changes in the last 7 days00
First seen (differs)2026-10-152026-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

module-gates

In its own words, on Community GitHub marketplaces:

Enforce module boundary contracts (readonly, no-new-exports) on Claude Code edits.

project-boundary

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

Blocks destructive commands outside the project directory. Allows file operations within the project (refactoring, cleanup) but prevents accidental damage outside it.

How to run each

module-gates As a Claude Code plugin

Claude Code
/plugin marketplace add cuzfrog/module-gates
/plugin install module-gates@cuzfrog

project-boundary As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install project-boundary@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: module-gates · What it can do: project-boundary · 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