agent-creator

An agent-design helper for turning a description of a desired autonomous coding assistant into an agent specification.

In plain words
What is it for?
Use it to create agents for tasks such as code review or other plugin-based autonomous work.
Why use it?
It removes the need to work out the agent’s role, responsibilities, success criteria, and project-specific instructions from scratch.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/smarks26/claude-plugin-template/agent-creator
Clone the repo
git clone --depth 1 https://github.com/smarks26/claude-plugin-template
Per session 254 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,615 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00254 $0.01615
Opus 5 $0.00127 $0.00807
Sonnet 5 $0.00051 $0.00323
Haiku 4.5 $0.00025 $0.00161

Measured 2d ago against content hash 99ca808b7577, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-creator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to agent-creator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/plugin-dev/agents/agent-creator.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 <example> 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 <example> blocks with:
      <example>
      Context: [Situation that should trigger agent]
      user: "[User message]"
      assistant: "[Response before triggering]"
      <commentary>
      [Why agent should trigger]
      </commentary>
      assistant: "I'll use the [agent-name] agent to [what it does]."
      </example>
      
    • 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

Read the full file on GitHub · 177 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 177 lines · 254 tokens per session scan A 99ca808b7577

Subscribe to this mod's changes

agent-creator is an agent published in the GitHub repository smarks26/claude-plugin-template (2 stars, last pushed 3mo ago), licensed MIT. It adds 254 tokens to every session and 1,615 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-creator, differing in 0 lines, and is treated as a copy.