add-agent

add-agent is a command for Claude Code from ivan-magda/claude-code-plugin-template. It costs 12 tokens per session (4,305 once invoked), scanned A, original, MIT.

A command for creating a new specialized sub-agent file inside a coding-agent plugin, with the required metadata and structure.

In plain words
What is it for?
Use it to add an agent with a kebab-case name to the current plugin or to a specified plugin. You can provide a description of the agent's task.
Why use it?
It avoids manually creating the agent folder and file and reduces setup mistakes. It works from either a plugin folder or a marketplace folder.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions .claude-plugin; mentions subagents; positional $N argument.

Part of the plugin-development plugin — 1 skill, 7 commands, 1 agent, 3 hooks shipped together

Good fit Use it to add an agent with a kebab-case name to the current plugin or to a specified plugin. You can provide a description of the agent's task.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ivan-magda/claude-code-plugin-template/add-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.

Clone the repo
git clone --depth 1 https://github.com/ivan-magda/claude-code-plugin-template

Made for: Claude Code.

Or install plugin-development, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 1 agent, 3 hooks.

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 add-agent

README.md
[![agentmods](https://agentmods.dev/badge/commands/ivan-magda/claude-code-plugin-template/add-agent/github.svg)](https://agentmods.dev/commands/ivan-magda/claude-code-plugin-template/add-agent)
Your own site
<a href="https://agentmods.dev/commands/ivan-magda/claude-code-plugin-template/add-agent"><img src="https://agentmods.dev/badge/commands/ivan-magda/claude-code-plugin-template/add-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 add-agent

Your own site · 80×15
<a href="https://agentmods.dev/commands/ivan-magda/claude-code-plugin-template/add-agent"><img src="https://agentmods.dev/badge/commands/ivan-magda/claude-code-plugin-template/add-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,305 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.00012 $0.04305
Opus 5.5 $0.00005 $0.01722
Sonnet 5.5 $0.00002 $0.00861
Haiku 4.5 $0.00001 $0.00430

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

Security

Grade A, and why

add-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 1mo 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

Copies of this mod

2 near-identical copies found in the catalogue:

  • add-agent — 100% identical, 0 lines differ
  • add-agent — 100% identical, 0 lines differ
plugins/plugin-development/commands/add-agent.md · 603 lines

How it starts

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

Add Agent

Create a new sub-agent file with proper frontmatter and structure.

Arguments

  • $1 (required): Agent name in kebab-case (e.g., code-reviewer)
  • $2 (optional): Description in quotes (e.g., "Reviews code for quality")
  • --plugin=<plugin-name> (optional): Specify which plugin to add the agent to

Usage:

# From within a plugin directory, with description
/plugin-development:add-agent code-reviewer "Reviews code for quality, security, and best practices"

# Without description (uses default)
/plugin-development:add-agent code-reviewer

# From marketplace root, specifying plugin
/plugin-development:add-agent code-reviewer "Reviews code for quality, security, and best practices" --plugin=plugin-development

Prerequisites

  • Must be run from either:
    • A plugin root directory (containing .claude-plugin/plugin.json), OR
    • A marketplace root directory (containing .claude-plugin/marketplace.json)
  • agents/ directory will be created if needed

Instructions

Validation

IMPORTANT: When running test commands for validation (checking directories, files, etc.), use require_user_approval: false since these are read-only checks.

  1. Detect context and target plugin (output thoughts during this process):

    a. Check if we're in a plugin directory:

    • Look for .claude-plugin/plugin.json in current directory
    • Output: "Checking for plugin directory..."
    • If found:
      • Output: "Found plugin.json - using current directory as target plugin"
      • Use current directory as target plugin
    • If not found:
      • Output: "Not in a plugin directory, checking for marketplace..."

    b. If not in plugin directory, check if we're in marketplace root:

    • Look for .claude-plugin/marketplace.json in current directory
    • If found:
      • Output: "Found marketplace.json - this is a marketplace root"
      • This is a marketplace root
    • If not found:
      • Output: "Error: Neither plugin.json nor marketplace.json found"
      • Show error and exit

Read the full file on GitHub · 603 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. 1mo ago First seen · 603 lines · 0 tokens per session scan A a92ea08dda23

Subscribe to this mod's changes

add-agent is a command published in the GitHub repository ivan-magda/claude-code-plugin-template (70 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 4,305 once invoked, about $0.0000 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-30.

Related

Other commands, from other repositories

atomic-help

Route a lost user to the right atomic verb, skill, agent, or binary subcommand. Bare invocation reads git state and recommends one next step. Topic keyword or freeform intent → focused pointer. tour → guided walkthrough of the system. Help router, not duplicated docs.

damusix/atomic-claude · 57 tokens

atomic-plan

Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.

damusix/atomic-claude · 54 tokens

follow-up

Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…

damusix/atomic-claude · 0 tokens

documentation

Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).

damusix/atomic-claude · 0 tokens

watch-ci

Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.

damusix/atomic-claude · 69 tokens

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens