Problem or Need
The agent-creator agent has tools: Write, Read but lacks Glob for discovering existing agents in the agents/ directory.
The edge cases section (line 185) mentions:
Conflicts with existing agents: Note conflict, suggest different scope/name
However, without Glob, the agent cannot proactively scan for existing agent files to detect naming conflicts before writing. It would need to rely on:
- The user mentioning existing agents
- Read failing on a specific path (reactive, not proactive)
Proposed Solution
Add Glob to the tools list:
This would allow the agent to:
- Check if
agents/ directory exists before attempting to create it
- List existing agent files to detect naming conflicts proactively
- Provide better conflict warnings with specific existing agent names
Which component would this affect?
Agent
Specific Component (if applicable)
agent-creator agent (plugins/plugin-dev/agents/agent-creator.md)
Alternatives Considered
- Leave as-is - The agent works, and conflict handling may be rare
- Add Bash instead - Could use
ls but Glob is more appropriate and follows least-privilege better
- Rely on loaded skill - The agent loads
agent-development skill, but skills provide knowledge not tool access
Additional Context
Found during comprehensive agent review against Claude Code plugin subagent best practices.
Current tools line (line 44):
Proposed change:
The addition of Glob is minimal and follows the principle of least privilege while enabling the conflict detection functionality mentioned in the edge cases.
How important is this feature to you?
Low - Just a suggestion
Problem or Need
The
agent-creatoragent hastools: Write, Readbut lacksGlobfor discovering existing agents in theagents/directory.The edge cases section (line 185) mentions:
However, without
Glob, the agent cannot proactively scan for existing agent files to detect naming conflicts before writing. It would need to rely on:Proposed Solution
Add
Globto the tools list:This would allow the agent to:
agents/directory exists before attempting to create itWhich component would this affect?
Agent
Specific Component (if applicable)
agent-creator agent (
plugins/plugin-dev/agents/agent-creator.md)Alternatives Considered
lsbut Glob is more appropriate and follows least-privilege betteragent-developmentskill, but skills provide knowledge not tool accessAdditional Context
Found during comprehensive agent review against Claude Code plugin subagent best practices.
Current tools line (line 44):
Proposed change:
The addition of
Globis minimal and follows the principle of least privilege while enabling the conflict detection functionality mentioned in the edge cases.How important is this feature to you?
Low - Just a suggestion