Plugin components
What a plugin can actually carry in each ecosystem. The overlap is deliberate — skills and MCP servers travel everywhere, hooks nearly so — which is why one plugin directory can serve several marketplaces: each tool reads its own manifest and the component types it understands.
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 | — | — | — | — |