[FEATURE] plugin private subagents/commands/mcp-servers
Resolved 💬 4 comments Opened Nov 3, 2025 by SpiGAndromeda Closed Jan 11, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Subagents are a good way to split a workflow, defined in a skill, into sub-tasks. But in this specific use case these subagents are only used by the spicifc skill. If they are in the same plugin, it would make sense to not expose the subagent if it's not required.
Its the same concept several programming languages use for modules: configure what is exposed publically.
Proposed Solution
The marketplace.json and plugin.json could provide a whitelist to specifiy what commands/agents/skills(?)/... should usuable in the context where the plugin is used.
Alternative Solutions
_No response_
Priority
Low - Nice to have
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗