Best Claude Code plugins 2026
A Claude Code plugin can add skills, agents, hooks and MCP servers to every session. Some of that runs code on your machine with your user permissions. This guide is the check I run before I install a plugin, and a short list of plugins I can back with a source.
Disclosure: I build OrchestKit, the first plugin on the list. Run the same checks on it.
What to check before you install
Skills
Skills enter Claude's context as instructions. Find out what loads on every turn and what loads only when a skill runs. After you install,
claude plugin detailswith the plugin's name prints the projected tokens it adds to every session.Hooks
Command hooks run shell commands with your full user permissions at every lifecycle event they register for, such as session start or before and after tool calls. Every hook runs outside the sandbox. Read the plugin's
hooks/hooks.json. Find out what each hook records and where it sends it.Agents
Agents are subagents the plugin adds. Check which tools each agent can use, and which MCP servers it expects you to supply yourself.
Permissions and trust
Anthropic does not review third-party marketplaces. Run
claude plugin marketplace listto see where each marketplace comes from, read the Will install section in/plugin, and read.mcp.jsonandbin/before you trust a plugin.Maintenance
Look at the last update, the release notes and the Claude Code version the plugin supports. Auto-update is on by default for the official marketplace and off by default for third-party marketplaces, so a third-party plugin stays on the version you installed until you update it or turn auto-update on.
The short list
This list has only plugins I can confirm from the plugin's own README or from Anthropic's documentation. The official catalog changes often, so browse it yourself for the rest.
1. OrchestKit
Third-party marketplace: yonatangross/orchestkit
One plugin with 110 skills, 36 agents and 162 hooks for production engineering: quality gates, git protection, and review and commit flows. MIT licensed and free. Hooks write lifecycle events to a local log, and that log never records prompt text or file contents. Some hooks also keep local notes in the project's .claude folder, including text from your commit messages. Remote sync is off unless you set it up. Needs Claude Code 2.1.277 or later.
Install:
/plugin marketplace add yonatangross/orchestkit, then/plugin install ork, then/ork:setup.2. Anthropic's own plugins
Official marketplace: claude-plugins-official
Claude Code adds the official marketplace for you. Most of its catalog comes from partners and other authors. Anthropic maintains a small set of its own plugins there, for example:
commit-commands: commands to commit, push and open pull requests.code-review: maintained by Anthropic. Open its details in/pluginto see what it installs.feature-dev: maintained by Anthropic. Open its details in/pluginto see what it installs.- Language server plugins for code intelligence.
Install one:
/plugin install commit-commands@claude-plugins-official.Anthropic's marketplaces (Claude Code docs)Plugin security and trust (Claude Code docs)
Fewer plugins, not more
Each plugin adds context, and a plugin with hooks adds code that runs on each event its hooks register for. Start with one plugin, measure what it costs, and keep it only if it earns its place.