agentsclimarketplace

Agent template

Skill claude-world/director-mode-lite/skills/agent-template

Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.From its SKILL.md

Install
npx -y skills add claude-world/director-mode-lite --skill agent-template

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 1 command, including `/agent-check`.

SKILL.md

3.6 KB, 900 tokens by cl100k_base, as published. Nobody here has run it

Agent Template Generator

Generate a custom agent file based on requirements.

Usage: /agent-template [agent-name] [purpose]


Templates

PurposeTemplateToolsColorModel
Review/AuditReviewerRead, Grep, Glob, Bashyellowinherit
Generate/CreateGeneratorRead, Write, Grep, Globcyaninherit
Fix/ModifyFixerRead, Write, Edit, Bash, Grepredinherit
Test/ValidateTesterRead, Bash, Grep, Globgreeninherit
DocumentDocumenterRead, Write, Grep, Globcyaninherit
OrchestrateOrchestratorRead, Write, Bash, Grep, Glob, Agentcyanhaiku

Process

  1. Gather Requirements

    • Agent name (lowercase, hyphenated)
    • Purpose
    • Tools needed
    • Model (fable/opus/sonnet/haiku/inherit — inherit is the recommended default)
    • Preloaded skills (if any)
  2. Select Template based on purpose

  3. Generate File at .claude/agents/[name].md

  4. Validate with /agent-check


Frontmatter Reference (official fields)

---
name: agent-name            # Required: lowercase, hyphenated, 3-50 chars
description: >              # Required: 200-1000 chars recommended, include <example> blocks.
  Use this agent PROACTIVELY when [triggering conditions]. Examples:
  <example>
  Context: [situation]
  user: "[request]"
  assistant: "[response]"
  <commentary>[why this agent]</commentary>
  </example>
color: cyan                 # Required by Director Mode convention (CI-enforced); optional per spec
model: inherit              # Required by Director Mode convention (CI-enforced); optional per spec.
                            #   Valid: fable, opus, sonnet, haiku, inherit, default, best, sonnet[1m],
                            #   opus[1m] (or a full model ID). inherit recommended. NOT opusplan.
effort: medium              # Optional: low, medium, high, xhigh, max
tools:                      # Optional: YAML list (omit = all tools)
  - Read
  - Write
  - Edit
  - Bash
  - Grep
  - Glob
  - Agent
  - WebFetch
  - WebSearch
  - TodoWrite
  - NotebookEdit
disallowedTools:            # Optional: explicit tool blocking
  - NotebookEdit
maxTurns: 20                # Optional: max agentic turns before stopping (positive integer)
skills:                     # Optional: preloaded skill names (list)
  - linked-skill
memory: project             # Optional: one of user, project, local
background: false           # Optional: run the agent in the background (boolean)
isolation: worktree         # Optional: run the agent in an isolated git worktree
---

Not supported in filesystem/plugin agent frontmatter — do not emit these: hooks, mcpServers, permissionMode (security restriction), and forkContext (not an official field). Agents fork automatically when dispatched.


Reviewer Template Structure

---
name: [name]
description: >
  Use this agent PROACTIVELY when [triggering conditions]. Examples:
  <example>
  Context: [situation]
  user: "[request]"
  assistant: "[response]"
  </example>
color: yellow
tools:
  - Read
  - Grep
  - Glob
  - Bash
model: inherit
skills:
  - linked-skill
# maxTurns: 20
# memory: project
---

# [Name] Agent

## Activation
When to trigger

## Review Checklist
- [ ] Check items

## Output Format
Report structure

Example

/agent-template security-scanner "scan code for vulnerabilities"

Output: Created .claude/agents/security-scanner.md

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most context ai engineering skills give in 900 tokens

Counted across 1,328 of the 2,349 authors here whose files we hold, read 2026-09-06

  • Dispatch a fresh subagent for each taskin 76 of 1328, across 59 files
  • Perform spec compliance review before code quality reviewin 44 of 1328, across 34 files
  • Dispatch a final code reviewer after all tasksin 38 of 1328, across 26 files
  • Answer subagent questions before allowing implementationin 36 of 1328, across 26 files
  • Use the least powerful model capable of the taskin 33 of 1328, across 26 files
  • Create a TodoWrite list for all tasksin 32 of 1328, across 22 files
  • Perform a task review after each implementationin 31 of 1328, across 24 files
  • Extract all tasks and context from the planin 29 of 1328, across 20 files
  • Provide full task text to subagentsin 28 of 1328, across 20 files
  • Use git worktrees for isolated workspacesin 25 of 1328, across 20 files
  • Specify the model explicitly when dispatching a subagentin 23 of 1328, across 18 files
  • Execute all tasks from the plan without stoppingin 21 of 1328, across 16 files

Said here and by no other author read

  • Gather agent name and purpose
  • Select template based on purpose
  • Validate file with agent-check

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.