Claude Code Mods

What are Claude Code mods

Mods run function hooks inside Claude Code to add interactive panels, respond to session events, or change tool behavior. Skills, MCP servers, and settings hooks are separate extensions available in the categories above.

Start with the result you want in a session. A context panel, an interface change, or an event-driven behavior belongs in the native mods list above. For reusable task instructions, browse Claude Skills; for external tools and data, browse MCP servers. The category cards show the actual number of listed projects, so you can see the available choices before opening a collection.

Plugins package related components for installation. Agents and subagents provide specialized workers, commands make recurring tasks easy to invoke, and a status line keeps selected session information visible. Settings-based hooks are listed separately from native function-hook mods. Open a detail page to compare the component’s purpose, source path, and setup requirements before choosing it for your project.

How to install

1. 1. Copy

   Open the source, check its requirements, then copy the setup command.

2. 2. Install

   Run it in Claude Code or a terminal as directed; replace example paths first.

3. 3. Reload

   Use Claude Code 2.1.287 or later and run /reload-plugins in your session.

Keep each command in its intended place: lines starting with claude run in a terminal, while slash commands run inside Claude Code. A local marketplace path is relative to the terminal’s current directory. When a setup begins by cloning a repository, preserve the following path or adjust it to the location where you actually saved that repository.

After installation, confirm the expected component is loaded and try one small task. Some entries share a parent plugin, so installing that bundle once may provide several listed capabilities. Follow the detail page for extra runtimes, authentication, or platform requirements. If an earlier step fails, resolve it before continuing with the rest of the copied command sequence.

How we review mods

• Check the source

  Each listing points to its maintainer’s repository or project documentation.

• Check the command

  Setup commands follow the instructions documented by the source.

• Explain the setup

  Project pages cover permissions, configuration, and usage notes.

For native mods, our source check looks for the plugin’s hook registration and its implementation files. Other extension types are checked against their own documented structure. Descriptions explain the listed component rather than attributing every feature in a large repository to one entry. This makes it easier to distinguish a focused tool from a collection that installs several workflows.

Repository stars and recent push dates are reference signals, not individual mod ratings or proof that an installation was tested on your machine. Entries from the same repository can share those numbers. Follow the source link for release notes and current compatibility. We update the catalog from repository evidence; listing a project is not an endorsement of every upstream change.