Plugins

What it is

A Plugin bundles several agent extensions into one installable package. Rather than wiring up commands, subagents, hooks, and MCP servers one at a time, a Plugin ships them together so you (or your team) can install the whole capability in a single step. It's the distribution unit for everything that customizes an AI coding agent.

Strengths

• One install brings a complete, coherent set of tools instead of piecemeal setup.
• Shareable, so a team or a community can standardize on the same workflow.
• Versioned and removable, so you can update or uninstall cleanly.
• Bundles different extension types — commands, hooks, agents, MCP — under one roof.

Trade-offs

• A Plugin runs with real access, so installing one you don't trust is a genuine risk.
• More layers to reason about when something behaves unexpectedly.
• Quality and upkeep depend on whoever publishes it.
• Overlapping plugins can collide on commands or behavior.

When to use it

Use a Plugin when you've assembled a workflow worth sharing or reusing across projects, or when you want to adopt someone else's packaged setup without rebuilding it by hand.

Vibe coding fit

Plugins turn a one-off setup into something portable. Once you've found a combination of commands and hooks that makes the agent reliable for your stack, packaging it as a Plugin means every new project starts from that baseline. Treat plugins like dependencies: install from sources you trust, and read what they add before enabling them.

// plugin.json — declare what a plugin provides
{
  "name": "team-workflow",
  "version": "1.0.0",
  "commands": "./commands",
  "hooks": "./hooks.json"
}