Plugin components
What a plugin can actually carry in each ecosystem. Every name in this row is a row of its own further up the matrix, which is the point: the overlap is what lets one plugin directory serve several marketplaces, because each tool reads its own manifest and takes the parts it understands. Claude Code carries four things nobody else does (executables, monitors, themes, workflows) and Codex carries connectors, so those have no row here yet.
Widest support first. Hover any name for what it means.
| concept | support | Claude Code | Codex | Cursor | Fabro not shipped | Kimi Code |
|---|---|---|---|---|---|---|
| Hooks | 4/5 | — | ||||
| mcpServers | 4/5 | — | ||||
| Skills | 4/5 | — | ||||
| Agents | 3/5 | — | — | |||
| Commands | 3/5 | — | — | |||
| apps | 1/5 | — | — | — | — | |
| Executables | 1/5 | — | — | — | — | |
| LSP servers | 1/5 | — | — | — | — | |
| Monitors | 1/5 | — | — | — | — | |
| Output styles | 1/5 | — | — | — | — | |
| Rules | 1/5 | — | — | — | — | |
| Settings | 1/5 | — | — | — | — | |
| Themes | 1/5 | — | — | — | — | |
| Workflows | 1/5 | — | — | — | — |