From director-mode-lite
Generates custom Claude Code agent.md files from purpose-based templates (Reviewer, Generator, Fixer, Tester, Documenter, Orchestrator). Configures tools, model, color; saves to .claude/agents/ and validates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/director-mode-lite:agent-templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a custom agent file based on requirements.
Generate a custom agent file based on requirements.
Usage: /agent-template [agent-name] [purpose]
| Purpose | Template | Tools | Color | Model |
|---|---|---|---|---|
| Review/Audit | Reviewer | Read, Grep, Glob, Bash | yellow | sonnet |
| Generate/Create | Generator | Read, Write, Grep, Glob | cyan | sonnet |
| Fix/Modify | Fixer | Read, Write, Edit, Bash, Grep | red | sonnet |
| Test/Validate | Tester | Read, Bash, Grep, Glob | green | sonnet |
| Document | Documenter | Read, Write, Grep, Glob | cyan | sonnet |
| Orchestrate | Orchestrator | Read, Write, Bash, Grep, Glob, Task | cyan | haiku |
Gather Requirements
Select Template based on purpose
Generate File at .claude/agents/[name].md
Validate with /agent-check
---
name: agent-name # Required: lowercase, hyphenated, 3-50 chars
description: > # Required: 200-1000 chars recommended, include <example> blocks
Use this agent when [triggering conditions]. Examples:
<example>
Context: [situation]
user: "[request]"
assistant: "[response]"
<commentary>[why this agent]</commentary>
</example>
color: cyan # Required: yellow, red, green, blue, magenta, cyan
tools: # Optional: YAML list (omit = all tools)
- Read
- Write
- Edit
- Bash
- Grep
- Glob
- Task
- WebFetch
- WebSearch
- TodoWrite
- NotebookEdit
model: sonnet # Required: inherit, haiku, sonnet, opus, best, sonnet[1m], opus[1m], opusplan
# forkContext: "true" # Optional: context isolation (string, not boolean)
# maxTurns: 20 # Optional: max agentic turns before stopping
skills: # Optional: skills to auto-load (array)
- linked-skill
# memory: # Optional: CLAUDE.md access (array)
# - user
# - project
# - local
# mcpServers: # Optional: MCP servers (string ref or inline config)
# - memory
# - name: custom-server
# type: stdio
# command: npx
# args: ["-y", "@example/server"]
hooks: # Optional: agent-scoped lifecycle hooks
PreToolUse:
- matcher: Write
hooks:
- type: command
command: ./scripts/validate.sh
PostToolUse:
- matcher: Bash
hooks:
- type: command
command: ./scripts/log.sh
Stop:
- hooks:
- type: command
command: ./scripts/check.sh
once: true
permissionMode: default # Optional: default, acceptEdits, bypassPermissions, plan, delegate, dontAsk
disallowedTools: # Optional: explicit tool blocking
- NotebookEdit
---
---
name: [name]
description: [brief purpose]
color: yellow
tools:
- Read
- Grep
- Glob
- Bash
model: sonnet
skills:
- linked-skill
---
# [Name] Agent
## Activation
When to trigger
## Review Checklist
- [ ] Check items
## Output Format
Report structure
/agent-template security-scanner "scan code for vulnerabilities"
Output: Created .claude/agents/security-scanner.md
npx claudepluginhub claude-world/director-mode-liteCreates Claude Code agents with YAML frontmatter for name, description, tools, model selection, and color. Use when adding specialized agents to plugins.
Guides creation of autonomous agents for Claude Code plugins, covering Markdown file structure, YAML frontmatter (name, description, model, color, tools), system prompts, triggering examples, and best practices.
Creates Claude Code agents from scratch or by adapting templates. Guides requirements gathering, template selection, and file generation following Anthropic best practices (v2.1.63+).