Publish a mod

Open one pull request. A bot runs the checks and comments the result. When every check passes, it merges, and your mod is listed within minutes.

1. Put your mod on GitHub

   Use a public github.com repo. Set name, version, description (200 characters or fewer), author and license in .claude-plugin/plugin.json. Add at least one test. Push a tag, for example v1.0.0.

2. Add one file to the catalog

   Fork baselane-sh/mods-catalog and add entries/my-mod.json. For a mod in a subfolder, use "source": "git-subdir" with url and path.

   {
     "name": "my-mod",
     "source": { "source": "github", "repo": "you/my-mod", "ref": "v1.0.0" },
     "category": "pane",
     "tags": ["git"],
     "screenshots": ["docs/screenshot.png"]
   }

   Categories: guard, pane, band, command, sound, style, stats, nudge, lifecycle, render.

3. Open a pull request

   Your first pull request waits until a maintainer approves the run. After that, your pull requests run at once. To update a mod, raise version, push a new tag and change ref.

The checks

1. Scope. Change exactly one file, under entries/. A maintainer handles removals and every other file.
2. Entry. Make the entry match the format on the submit page, and pick a name that is not taken.
3. Owner. Only the first submitter can update a mod. Ask a maintainer to move the mod to you.
4. Tag. Push the tag to a public github.com repo and put the tag name in source.ref.
5. Manifest. In .claude-plugin/plugin.json set name (equal to the entry name), version (semver), description (200 characters or fewer), author and license.
6. Is a mod. A mod has hooks/hooks.json that points to its hooks module.
7. Validate. Run claude plugin validate on the mod folder and fix what it reports.
8. Size and shape. Keep the mod at 10 MB or less, with no top-level bin/ and no symlink that leaves the mod. Each screenshot is 2 MB or less.
9. Tests. Run claude plugin test on the mod folder. At least one test must run and every test must pass.
10. Version. Raise version in plugin.json. Users get new code only when the version changes.

Verified

A maintainer reads the code at the pinned commit and adds the mod to the verified list. When the mod updates to a new commit, the badge drops until someone reviews it again. Mods without the badge passed the automated checks only.

Removal

A maintainer can remove a mod from the catalog. Claude Code then uninstalls it at the next session start, but only for people whose copy of the gallery is current. Auto-update is off by default, so ask your users to turn it on.