create-sub-agent

create-sub-agent is a skill for Claude Code from tsmztech/claude-code-plugins. It costs 23 tokens per session (365 once invoked), scanned A, original, MIT.

A guided tool for creating a Claude Code sub-agent, a separate assistant with its own instructions and tool permissions.

In plain words
What is it for?
Use it to create project-level or personal sub-agents for focused development tasks.
Why use it?
It helps choose the right location, model, permissions, and optional integrations while following Claude Code's required file format.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-craft plugin — 4 skills, 2 commands shipped together

Good fit Use it to create project-level or personal sub-agents for focused development tasks.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add tsmztech/claude-code-plugins
Claude Code
/plugin install claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 4 skills, 2 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-sub-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-sub-agent/github.svg)](https://agentmods.dev/skills/tsmztech/claude-code-plugins/create-sub-agent)
Your own site
<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/create-sub-agent"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-sub-agent/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-sub-agent

Your own site · 80×15
<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/create-sub-agent"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-sub-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 365 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00023 $0.00365
Opus 5.5 $0.00009 $0.00146
Sonnet 5.5 $0.00005 $0.00073
Haiku 4.5 $0.00002 $0.00036

Measured 2mo ago against content hash cf37c7ffb530, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-sub-agent 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 2mo 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.

claude-craft/skills/create-sub-agent/SKILL.md · 34 lines

What it actually says

Create a Claude Code Sub-Agent

Read first: ${CLAUDE_PLUGIN_ROOT}/docs/sub-agents.md — this is the full reference for sub-agent structure, frontmatter fields, permission modes, hooks, and examples. Use it to guide every decision.

Determine target location

Check if the user passed a path as $ARGUMENTS.

  • Path given → create at <path>/.claude/agents/<sub-agent-name>.md
  • personal → create at ~/.claude/agents/<sub-agent-name>.md
  • Nothing → ask where. Explain project vs personal scope (see "Choose the subagent scope" in the doc)

Gather requirements

Ask the user what the sub-agent should do. From their answer, use the doc to determine:

  • What the system prompt should contain (see "Write subagent files")
  • Which tools it needs and which to deny (see "Available tools")
  • Which model fits — haiku for fast/cheap, sonnet for balanced, opus for complex, inherit for same as parent (see "Choose a model")
  • Whether it needs a specific permission mode (see "Permission modes")
  • Whether it needs preloaded skills, persistent memory, MCP servers, or hooks (see respective sections in the doc)

Create the sub-agent

Follow the conventions from the doc for file format and naming. Check if the target already exists before writing — never overwrite without asking.

After creating, tell the user how to test it.

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. 2mo ago First seen · 34 lines · 23 tokens per session scan A cf37c7ffb530

Subscribe to this mod's changes

create-sub-agent is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens