claude-code-mods repository reference

A map of modmyclaude/claude-code-mods: what is written by hand, what a script generates, and how a change reaches installed copies.

Repository map

Paths, ownership and purpose
Path	Kind	Purpose
`prompts/<mod>.md`	Hand-written	The prompt that builds a mod, with catalogue frontmatter.
`prompts/starters/`	Hand-written	Starter prompts such as Mod Maker and Mod Matchmaker.
`mods/<mod>/`	Hand-written	The plugin: manifest, hooks module, tests and README.
`scripts/`	Hand-written	Check, smoke install, links, catalogue and version scripts.
`CHANGELOG.md`	Hand-written	One line per shipped mod change.
`.claude-plugin/marketplace.json`	Generated	The marketplace Claude Code installs from.
`site/mods.json`	Generated	Catalogue data. This website reads it.
`README.md catalogue and badges`	Generated between markers	The mod tables and badge row.

Prompts are the source of each mod, mods are the plugins, starters help you write new prompts, and scripts check and generate.

Never hand-edit generated files

build-catalog.mjs reads each prompt's frontmatter, each plugin.json and the validator report, then writes the marketplace, the README catalogue and site/mods.json. CI runs it with --check and fails if the committed files are out of date.

npm run catalog

Drafts stay out

A prompt with draft: true in its frontmatter keeps its mod out of the catalogue. The script also skips a prompt whose mod is not built yet, and a mod whose manifest is not committed. Drafts need no version bump.

The repository's site folder and this website

The repository's site/ folder holds a static gallery and its mods.json data. This website is a separate project. It ships a bundled copy of that catalogue data and reads the published file when available, but its pages, guides and these docs are its own. These docs are written from a pinned review, not fetched from GitHub when you load the page.

Versions and the CHANGELOG

Installed copies get a change through /plugin update only when the version moves. Any change to what a mod ships, its hooks/, types/, sounds and other assets or plugin.json, bumps version and adds one CHANGELOG.md line. README or test changes alone need none. CI checks this on every push and pull request; run it locally before pushing:

npm run versions -- origin/main

Scripts

Run from the root of a local clone after npm ci, with Node 20 or later and Claude Code 2.1.287 or later.

Replace <mod> with a mod name, such as redline, before running a command.

npm run check -- mods/<mod>   # validate, tsc when types exist, tests
npm run smoke                 # install every mod into a throwaway config
npm run links                 # relative links and images resolve
npm run catalog               # regenerate generated files
npm run catalog:check         # fail if generated files are stale

For gate details see testing and compatibility.

Sources

Source-reviewed on 15 Oct 2026 against modmyclaude/claude-code-mods at commit 8628e8f. This page describes what the repository files say and do. We did not run the repository's tests or a new live Claude Code session for it.

All docs · Guides · Browse mods · Install mods