01 / Check your Claude Code version
Run this in your shell. Terminal mods require 2.1.287 or later. If your CLI is older, use the official installation documentation to choose an update method; this site does not update your CLI.
claude --version02 / Review the source and trust boundary
Inspect the plugin manifest, hooks/hooks.json, every registered module, imported files, and external dependencies at the listed commit SHA. Read license terms separately. A public GitHub repository is not automatically open source.
Mods run with your user permissions. Process execution, MCP, custom APIs, and tool argument rewriting can introduce indirect capabilities that a short list of direct calls cannot explain. Review credentials, downstream services, and costs before enabling a connector.
03 / Validate a local copy
After obtaining a local source copy at the recorded SHA, run validate in your shell. Replace the example path with that plugin directory. Inspect the hooks, calls, and environment-read inventory using a supported CLI. Validation does not execute an installation and does not certify code safety.
If validation fails, does not list the registered modules, or uses an unsupported version, keep permissions unverified. A manifest-only success does not prove a modern function mod can load.
claude plugin validate ./some-mod04 / Add a marketplace to install Claude mods
Copy the two verified commands from a mod detail page. Enter the first line in the Claude Code prompt to add its marketplace, then the second line to install that exact plugin. These slash commands are not shell commands.
If the listing says Marketplace installation not verified, visit the source repository. Do not invent a marketplace name. External service setup is a separate step, never an appended install script.
05 / Check the active plugin
Open the plugin manager in the Claude Code prompt and confirm the intended plugin is active. Follow its source instructions for commands, panes, or configuration. Install one mod at a time so you can identify the cause if behavior changes.
Copied means the clipboard received text. It does not mean the marketplace was added, installation succeeded, or the mod is compatible.
/plugin06 / Disable or uninstall one plugin
In Claude Code, open /plugin and use the installed-plugin controls to disable or uninstall the specific plugin. You can also use the supported CLI commands below in your shell, replacing the example with the plugin’s exact name@marketplace identifier. Disable preserves the installation; uninstall removes it.
claude plugin disable name@marketplace-name
claude plugin uninstall name@marketplace-name07 / Troubleshoot a single session
Start a new session with safe mode to isolate third-party plugin behavior. This is a per-session troubleshooting option, not permanent removal. Safe mode does not disable built-in mods.
If a mod changes tool calls or prompts unexpectedly, stop using it, disable that plugin, and review its source and configuration. Report public source facts rather than private terminal logs or secrets.
claude --safe-modeFrequently asked questions
Where do the two install commands go?
Enter /plugin marketplace add and /plugin install in the Claude Code prompt, in that order. Version checks, validate, disable/uninstall CLI commands, and --safe-mode belong in your shell.
Does validate prove a mod is safe?
No. Validation provides capability evidence for the inspected source and CLI version. It is not a sandbox, a guarantee, or a substitute for reviewing indirect behavior.
Does safe mode disable built-in mods?
No. Safe mode is a single-session diagnostic for third-party behavior; built-in mods remain enabled.