Skip to content

Build your own plugin or marketplace

Last reviewed October 24, 2026

A plugin is a package of add-ons for a coding agent that people install, update and remove in one step. It can hold skills, slash commands, subagents, hooks that run on the agent's events, and MCP servers. A marketplace is a catalog: one file that lists plugins and where to fetch each. People add a marketplace once, then install its plugins by name.

A plugin, a marketplace or just a skill?

If what you have is one folder with a SKILL.md, publish the skill on its own (build your own skill). Every agent that reads skills can use it, and nobody has to trust a hook. Build a plugin when your skills need a hook or a server to work, or when several pieces belong together and should update together. A server that gives the agent new access has its own guide (build your own MCP server); a plugin is one way to ship it.

You need a marketplace as soon as you want people to install your plugin by name. It can be the same repository as the plugin.

Which agents load plugins

Claude Code, Codex, Copilot CLI, Cursor and Antigravity all load plugins, and Gemini CLI loads the same kind of package under the name extension. They agree on the shape: a manifest that names the plugin, with folders beside it, skills/ first among them. Where the manifest goes, and what else it may hold, differs. Copilot CLI loads a Claude Code plugin as it is, and Codex, Cursor and Copilot CLI share an open format. The second step covers each.

The six steps

  1. 1. Build a plugin

    The manifest and folders of a Claude Code plugin, trying it before you publish, and a complete example that validates.

  2. 2. Plugins for other agents

    The Agent Plugins format, and what Codex, Gemini CLI, Antigravity, Copilot CLI and Cursor each expect.

  3. 3. Make a marketplace

    The marketplace file, where it can fetch each plugin from, pinning, and how people add it and install from it.

  4. 4. Publish a plugin

    Versions and updates, a README people trust, the official directories, and getting listed here.

  5. 5. Make a plugin safe to install

    Plugins run code with their user's privileges: hooks, servers, pinned sources and secrets kept out of manifests.

  6. 6. Plugin checklist

    Findable, trustworthy, maintainable: what to check before you tell anyone about it.