A Claude Code plugin is a package that adds to Claude Code in one install: slash commands, specialist subagents, hooks that run on events, skills and MCP servers. Instead of copying files between machines, a team installs the same plugins and everyone gets the same workflow.

Plugins listed here
5
Free to install
5

What is inside a plugin

your-plugin/
  • .claude-plugin/
  • plugin.jsonname, version, description
  • commands/slash commands, one Markdown file each
  • review.mdbecomes /your-plugin:review
  • agents/subagents with their own instructions and tools
  • skills/skills that load when a task fits
  • hooks/
  • hooks.jsoncommands that run on events
  • .mcp.jsonMCP servers the plugin brings with it
Every part is optional except plugin.json. Most plugins use two or three of them.
PartWhat it doesYou use it by
CommandsA saved instruction with argumentsTyping /plugin-name:command
AgentsA specialist that works in its own contextAsking for it, or Claude choosing it
HooksA script that runs on an event, such as before a tool runsNothing: it runs on its own
SkillsKnow-how loaded when a task fitsNothing: Claude loads it when relevant
MCP serversAccess to outside tools and dataAsking a question that needs them

How to install a plugin

Plugins are published in marketplaces: a list of plugins in a git repository or at a web address. Vayleer runs one marketplace for every plugin listed here. Add it once, then install any plugin in it. Both commands run inside Claude Code:

Inside Claude Code2 commands, in order
/plugin marketplace add https://vayleer.com/plugins/marketplace.json/plugin install failsafe@vayleer

Type /plugin on its own to browse marketplaces, turn plugins on and off, or remove them. To give a whole team the same setup, list the marketplace and plugins in the project’s .claude/settings.json; teammates are offered them when they trust the folder.

Hooks: the part that can say no

Hooks run on their own, whether or not Claude remembers to. A PreToolUse hook sees every command before it runs and can block it, ask you first or let it through.

hooks/hooks.json
{  "hooks": {    "PreToolUse": [      {        "matcher": "Bash",        "hooks": [          {            "type": "command",            "command": "${CLAUDE_PLUGIN_ROOT}/scripts/check-command.js"          }        ]      }    ]  }}
EventWhen it runsTypical use
PreToolUseBefore a tool runsBlock destructive commands or secrets in files
PostToolUseAfter a tool runsFormat code, run a linter on what changed
UserPromptSubmitWhen you send a messageAdd context, such as the current ticket
SessionStartWhen a session startsLoad project notes
StopWhen Claude finishesRun tests, send a notification

Plugins to try

FailSafe

Plugin by Dude Lemon LLC
Free

Best forstopping a destructive command before it runs

FailSafe blocking rm -rf ~ /tmp/build-cache in Claude Code: the stray space makes it delete the home folder
FailSafe: A typo that would wipe a home folder, stopped before it runs
  • Blocks the catastrophic, such as rm -rf of a home folder, and asks before force pushes, hard resets and dropped tables
  • Reads whole commands, including what is wrapped in sudo, env or bash -c
  • A small local script: nothing leaves your machine

KeySafe

Plugin by Dude Lemon LLC
Free

Best forkeeping API keys out of code and commits

KeySafe blocking a live Stripe secret key written into src/pay.js, then allowing it in a gitignored .env file read through process.env
KeySafe: A live key kept out of the code, and put where it belongs
  • Blocks live keys written into code, with a note to use an environment variable instead
  • Checks staged lines before a commit, across 35 key formats
  • Leaves test keys and placeholders alone

CommitWise

Plugin by Dude Lemon LLC
Free

Best forcommit messages and pull requests in your repository’s own style

CommitWise /commitwise:commit reading the staged diff and the last commits, then proposing a Conventional Commits message
CommitWise: A commit message in the style your history already uses
  • Matches the convention your recent commits already use, including Conventional Commits
  • Splits a large change into commits with one concern each, and shows the plan first
  • Nothing is committed until you agree
SearchReady

Technical SEO audits in Claude Code, traced to the file and line to fix

Free
CrossCheck

AI code review for Claude Code: security, accessibility and performance

Free
Browse every pluginEach listing shows the two commands to install it from the Vayleer marketplace.

Questions people ask

What is the difference between a plugin and a skill?

A skill is one piece of know-how. A plugin is a package that can contain skills along with commands, agents, hooks and MCP servers, installed together.

Where do Claude Code plugins come from?

From marketplaces: a git repository or web address with a list of plugins. Anyone can publish one, so check the reviews and the source code before you install.

Can a hook stop Claude from running a command?

Yes. A PreToolUse hook can block a command outright, ask you to confirm it, or allow it, before it runs.

How do I turn a plugin off?

Type /plugin in Claude Code, choose the plugin and disable or uninstall it.