About this directory
A community-run directory of Claude Code mods and extensions, with a plain record of what was checked.
Unofficial, and not a security service
Note
Unofficial community directory. Not affiliated with or endorsed by Anthropic.
This site does not host, package or run any extension. Each entry points to the publisher's own source. Listing something here is not an endorsement and not a safety claim, and nothing on this site says a listing was reviewed or scanned.
What a mod is
A mod is a Claude Code plugin whose behaviour lives in a hooks module: one register(on, options) entry that hooks the engine's events as functions.
Anthropic publishes 4 mods that ship inside Claude Code, with their source in the anthropics/claude-code repository.
Their listings carry this notice: Early access. Hooks modules load only where function hooks are enabled, and the API these mods are written against may change between releases without notice. They are not listed in the repository's marketplace; the copies that matter are the ones already in your Claude Code.
Browse the mods to see what each one does and where its source is.
The other kinds of extension
- Plugin
A package that can bundle commands, agents, skills, hooks and MCP servers, installed from a plugin marketplace.
- Skill
A folder with a SKILL.md file that teaches Claude how to do one kind of task.
- Agent
A subagent defined in a markdown file, with its own prompt and its own tools.
- Hook
A command that Claude Code runs on its own when a lifecycle event fires.
- MCP server
A Model Context Protocol server that gives Claude access to tools and data, added with claude mcp add.
- Command
A slash command defined in a markdown file.
Where the data comes from
Maintainers keep entries in src/data/catalog.json. Community entries are one file each in src/data/community/, added by pull request; see Publish. Every entry is validated against a schema when the site builds.
The catalog was generated on and holds 35 entries. Descriptions, publishers, licenses and install commands were written from the source pages linked on each entry. Star counts, where shown, carry the date they were captured. There are no download counts because no registry exists to measure them.
What Source verified means
Warning
Source verified means the source URL responded. It is not a security review.
Source verified means the entry's source URL returned HTTP 200 on the date shown on the entry. It says the source exists and is public. It says nothing about what the code does, who maintains it, or whether it is safe.
Check it yourself
Two scripts in the repository re-run the checks. The first requests every URL in the catalog and exits with an error if any of them does not respond with HTTP 200. The second confirms that plugin and mod entries have the manifest files they should, such as .claude-plugin/plugin.json.
npm run catalog:verifynpm run catalog:structurePassing runs repeat the claims already on the page. To decide whether something is safe to install, follow the checks on the Security page.
Ideas are not entries
The marketplace spec also describes 8 mods that nobody has published. They are kept on the Ideas page, apart from the directory, its counts and its search, and they cannot be installed.
Analytics
This site uses Vercel Web Analytics to count page views. Vercel states that it works without third-party cookies, identifies a visitor by a hash created from the incoming request, and discards that session after 24 hours. The site sets no cookies of its own; your light or dark theme choice is kept in your browser's local storage.
Read Vercel's privacy and compliance notes (opens in a new tab) for what is collected.