[FEATURE] plugin private subagents/commands/mcp-servers

[SpiGAndromeda]

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

[rinaldodev]

tl;dr: This is crucial for saving scarce context tokens in the main agent, not just for "separation of concerns." IMO, this makes the priority higher than "Low."

---

This would be really good for saving context usage in the main agent for the real work.

When the amount of available MCP/tools/commands/subagents start to grow, the main Claude agent starts to consume a lot of context tokens just to list/define the available servers and tools, reducing the actual usable context size for real work.

Moving all of that token usage to subagents'/plugins' own context would be great for building a tool that can handle more complex tasks. In a world where context tokens are a scarce resource, the separation of concerns in just a small bonus IMO.

We would be able to, for example, expose just the necessary bits (like a single subagent) to the main agent, saving context tokens for real important work.

That said, IMO this is higher than "Low - Nice to have".

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.