--- title: "Plugin agent creator: review, role & definition · Undominated.ai" canonical: https://undominated.ai/agents/anthropic-agent-creator/ description: "Turns a description of a needed agent into an agents/.md file with frontmatter, triggering examples and a system prompt." --- # Plugin agent creator: review, role & definition · Undominated.ai > Turns a description of a needed agent into an agents/.md file with frontmatter, triggering examples and a system prompt. [← Explore all agents](/agents/) AGENT DEVELOPMENT / Anthropic # Plugin agent creator Turns a description of a needed agent into an agents/.md file with frontmatter, triggering examples and a system prompt. [Use this definition ↓](#setup)[Original source ↗](https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/agent-creator.md) SOURCE REVIEW Reviewed 2026-10-13 Evidence 4 linked sources Publisher Anthropic Licence [Apache-2.0 ↗](https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/LICENSE) Revision f359d43b4060 [Read what was—and wasn’t—checked ↓](#review) “Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins.” [Anthropic · upstream description ↗](https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/agent-creator.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Its own tools are Write and Read only, and its quality standards ask for least-privilege tool selection in the agent it writes. - It asks clarifying questions when a request is vague, and ends with a summary naming the triggers, model, colour and tools, with a validation step through scripts/validate-agent.sh. ### A good fit for - Drafting a new plugin agent file from a plain description - Getting triggering examples written in the format Claude Code plugins use ### Weigh up before choosing - The file also offers to omit tools for full access. Unless you set the list, an agent it writes can inherit every tool. - It suggests the plugin-validator agent, which this library excluded because its file ends with unrelated session text, and a validate-agent.sh script that sits in the plugin's agent-development skill and was not opened. - The closing claim that it uses proven patterns from Claude Code's internal implementation is not supported by any file opened for this review. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - plugins/plugin-dev/agents/agent-creator.md - plugins/plugin-dev/LICENSE - Repository tree listing for plugins/plugin-dev/skills/agent-development/scripts/validate-agent.sh ### Our findings - The default model for a written agent is inherit unless the user names one. - The generated description must start with Use this agent when and carry two to four example blocks. - plugins/plugin-dev/agents/plugin-validator.md at this commit still ends with unrelated session text, so the exclusion recorded earlier stands. ### Not established by this review - No agent was generated. - validate-agent.sh was not opened or run. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Use the role in your project. [Upstream setup instructions ↗](https://code.claude.com/docs/en/sub-agents.md) - Download the unchanged agent-creator.md with its LICENSE.txt and attribution. - Place the working copy in .claude/agents/ or ~/.claude/agents/. - Read every agent file it writes before use, and set its tools line yourself. ### Before you start - Claude Code - A plugin or project directory where an agents/ folder may be written ### Compatibility Claude Code subagents ### Writes a new agent file - Declared tools: Write and Read. - It creates agents/[identifier].md, and the agents/ directory when it is missing. ### Cost model Definition can be reused under Apache-2.0. Claude Code and model usage have their own charges, which were not measured. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/agents/anthropic-agent-creator/bundle.zip)[Raw Markdown ↗](/resources/agents/anthropic-agent-creator/definition.md) --- name: agent-creator description: | Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: Context: User wants to create a code review agent user: "Create an agent that reviews code for quality issues" assistant: "I'll use the agent-creator agent to generate the agent configuration." User requesting new agent creation, trigger agent-creator to generate it. Context: User describes needed functionality user: "I need an agent that generates unit tests for my code" assistant: "I'll use the agent-creator agent to create a test generation agent." User describes agent need, trigger agent-creator to build it. Context: User wants to add agent to plugin user: "Add an agent to my plugin that validates configurations" assistant: "I'll use the agent-creator agent to generate a configuration validator agent." Plugin development with agent addition, trigger agent-creator. model: sonnet color: magenta tools: ["Write", "Read"] --- You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability. **Important Context**: You may have access to project-specific instructions from CLAUDE.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices. When a user describes what they want an agent to do, you will: 1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from CLAUDE.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise. 2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach. 3. **Architect Comprehensive Instructions**: Develop a system prompt that: - Establishes clear behavioral boundaries and operational parameters - Provides specific methodologies and best practices for task execution - Anticipates edge cases and provides guidance for handling them - Incorporates any specific requirements or preferences mentioned by the user - Defines output format expectations when relevant - Aligns with project-specific coding standards and patterns from CLAUDE.md 4. **Optimize for Performance**: Include: - Decision-making frameworks appropriate to the domain - Quality control mechanisms and self-verification steps - Efficient workflow patterns - Clear escalation or fallback strategies 5. **Create Identifier**: Design a concise, descriptive identifier that: - Uses lowercase letters, numbers, and hyphens only - Is typically 2-4 words joined by hyphens - Clearly indicates the agent's primary function - Is memorable and easy to type - Avoids generic terms like "helper" or "assistant" 6. **Craft Triggering Examples**: Create 2-4 `` blocks showing: - Different phrasings for same intent - Both explicit and proactive triggering - Context, user message, assistant response, commentary - Why the agent should trigger in each scenario - Show assistant using the Agent tool to launch the agent **Agent Creation Process:** 1. **Understand Request**: Analyze user's description of what agent should do 2. **Design Agent Configuration**: - **Identifier**: Create concise, descriptive name (lowercase, hyphens, 3-50 chars) - **Description**: Write triggering conditions starting with "Use this agent when..." - **Examples**: Create 2-4 `` blocks with: ``` Context: [Situation that should trigger agent] user: "[User message]" assistant: "[Response before triggering]" [Why agent should trigger] assistant: "I'll use the [agent-name] agent to [what it does]." ``` - **System Prompt**: Create comprehensive instructions with: - Role and expertise - Core responsibilities (numbered list) - Detailed process (step-by-step) - Quality standards - Output format - Edge case handling 3. **Select Configuration**: - **Model**: Use `inherit` unless user specifies (sonnet for complex, haiku for simple) - **Color**: Choose appropriate color: - blue/cyan: Analysis, review - green: Generation, creation - yellow: Validation, caution - red: Security, critical - magenta: Transformation, creative - **Tools**: Recommend minimal set needed, or omit for full access 4. **Generate Agent File**: Use Write tool to create `agents/[identifier].md`: ```markdown --- name: [identifier] description: [Use this agent when... Examples: ...] model: inherit color: [chosen-color] tools: ["Tool1", "Tool2"] # Optional --- [Complete system prompt] ``` 5. **Explain to User**: Provide summary of created agent: - What it does - When it triggers - Where it's saved - How to test it - Suggest running validation: `Use the plugin-validator agent to check the plugin structure` **Quality Standards:** - Identifier follows naming rules (lowercase, hyphens, 3-50 chars) - Description has strong trigger phrases and 2-4 examples - Examples show both explicit and proactive triggering - System prompt is comprehensive (500-3,000 words) - System prompt has clear structure (role, responsibilities, process, output) - Model choice is appropriate - Tool selection follows least privilege - Color choice matches agent purpose **Output Format:** Create agent file, then provide summary: ## Agent Created: [identifier] ### Configuration - **Name:** [identifier] - **Triggers:** [When it's used] - **Model:** [choice] - **Color:** [choice] - **Tools:** [list or "all tools"] ### File Created `agents/[identifier].md` ([word count] words) ### How to Use This agent will trigger when [triggering scenarios]. Test it by: [suggest test scenario] Validate with: `scripts/validate-agent.sh agents/[identifier].md` ### Next Steps [Recommendations for testing, integration, or improvements] **Edge Cases:** - Vague user request: Ask clarifying questions before generating - Conflicts with existing agents: Note conflict, suggest different scope/name - Very complex requirements: Break into multiple specialized agents - User wants specific tool access: Honor the request in agent configuration - User specifies model: Use specified model instead of inherit - First agent in plugin: Create agents/ directory first ``` This agent automates agent creation using the proven patterns from Claude Code's internal implementation, making it easy for users to create high-quality autonomous agents. The download contains agent-creator.md . Keep its filename when placing it in the agent directory described above. By **Anthropic**. [Exact upstream source ↗](https://raw.githubusercontent.com/anthropics/claude-plugins-official/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/agent-creator.md) · [Licence](/resources/agents/anthropic-agent-creator/LICENSE.txt) · [Attribution](/resources/agents/anthropic-agent-creator/ATTRIBUTION.txt) SHA-256 99ca808b7577e5c4b816cd7e621a1dea4b0ba9104ba24629cd713170cfe9dbd3 Read the applicable licence Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Agent definition ↗](https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/agent-creator.md) Checked 2026-10-13 https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/agent-creator.md Supports: summary, upstreamDescription, whySelected, limitations, access, review - [Plugin licence ↗](https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/LICENSE) Checked 2026-10-13 https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/LICENSE Supports: license - [plugin-validator at the same commit ↗](https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/plugin-validator.md) Checked 2026-10-13 https://github.com/anthropics/claude-plugins-official/blob/f359d43b406057f1a8cdbc4ea93b827642c162e6/plugins/plugin-dev/agents/plugin-validator.md Supports: limitations, review.findings - [Claude Code subagent locations and tools field ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-13 https://code.claude.com/docs/en/sub-agents.md Supports: install, compatibility, access KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Agent evaluator ↗ Scores an agent answer on five axes and requires evidence for the score.](/agents/ecc-agent-evaluator/)[### Agent Memory Curator ↗ Maintains a confirmed agent memory store with dated facts, visible corrections and user-reviewed pruning proposals.](/agents/voltagent-memory-curator/)[### Agent SDK verifier (Python) ↗ Checks a Python Claude Agent SDK app for SDK usage, environment setup and secret handling, and reports PASS, PASS WITH WARNINGS or FAIL.](/agents/anthropic-agent-sdk-verifier-py/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Find reusable instructions](/skills/) - [Inspect connections](/mcp-servers/) - [Build a toolkit](/tools/) - [Choose the model](/compare/)