Add your mod

1. Put a topic on your repository

Give your public GitHub repository one of these topics:

• claude-code-mods
• claude-mods
• claude-code-mod
• function-hooks

When ModsCode crawls GitHub it searches for these topics, and reads each mod it finds at the latest commit of the repository's default branch. It reads the source as text and never runs it. It crawls once a day: a new mod, or a new commit, is read the next day.

2. Make sure it is a mod

• The repository is public, and is not archived or a fork.
• The mod's folder holds .claude-plugin/plugin.json and hooks/hooks.json, and hooks.json has a modules list that names the files holding its code.
• The name in plugin.json is up to 64 characters of letters, digits, ., _ and -, and starts with a letter or digit.

3. The rule decides

A mod is listed when its code is laid out so a reader can check it: every module read, all its code inside the mod, nothing minified, evaluated or encoded, and every call outside made through $ in the open. The rules page lists the checks and how many mods fail each. A mod that does not pass gets no page.

An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD or CC0) with its text in the repository lets ModsCode show your code on the mod's page. Without one, the mod is still listed and its code is linked.

Being listed is not an endorsement. ModsCode does not vouch for any mod: each page shows what the code reaches, and readers check it themselves.