Start with a source you can inspect
A Claude Code plugin can include instructions, commands, agents, hooks and tool servers. Read the source documentation, license and requirements before installing. In a terminal session, /plugin opens the plugin browser; Discover lists packages from your added marketplaces.
Anthropic’s official marketplace is normally added automatically at the first interactive terminal session, subject to managed policy. For another marketplace, add its verified repository or local path first. See how marketplaces work.
Pick the install scope
| Scope | Who gets it | Use when |
|---|---|---|
| User | You, across projects on this computer | You want a recurring personal tool |
| Project | Collaborators through repository settings; they still install locally | The team deliberately shares this setup |
| Local | You, in this repository | You are evaluating it in a project |
Scope changes which settings enable the package. It is not a sandbox or a restriction on everything its code can access.
Install a known package
This example installs Frontend Design in local scope from the official marketplace. It is shown as a shell command, not a command to run inside the Claude prompt.
claude plugin install frontend-design@claude-plugins-official --scope localInside a Claude Code session, /plugin install frontend-design@claude-plugins-official opens the package details so you can review components and choose the scope. Read the installation summary and follow its loading instructions.
Check that the session loaded it
- Inspect the Installed tab and any loading errors.
- Use
claude plugin listin your shell to inspect installed packages. - Look in the command picker for namespaced plugin commands.
- If the summary asks for a reload, run
/reload-plugins. A package with an MCP server may also need runtime or authentication setup.
If the package is installed but unavailable, check its enabled scope, prerequisites and current session before reinstalling it. Consult the official troubleshooting guide.
Trying the Mods samples
Mods require Claude Code v2.1.287 or later. Their handlers run inside Claude Code with your privileges, outside its Bash sandbox. The sample detail pages show the repository clone, validation and --plugin-dir sequence from their own READMEs.
claude plugin validate ./some-mod can list hooks and calls without loading the mod. That is a useful review aid; it is not a proof that the source is safe. Check the sample’s actual source and compatibility notes first.
Browse the three documented sample Mods. To stop a specific installed mod, disable its plugin in /plugin. For one diagnostic session, claude --safe-mode also disables other user customizations. It does not disable built-in or managed behavior universally; check the official documentation.