create-agent

An interactive command for creating a specialized coding agent for a project. It gathers the role, responsibilities, experience, expertise, tools, and background needed for the new agent.

In plain words
What is it for?
Use it to create agents such as database performance experts, security specialists, or other role-focused assistants.
Why use it?
It turns a general request into a project-specific agent definition and registers the generated file in .claude/agents/.

Command for Claude Code

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 commands/bijutharakan/multi-agent-squad/create-agent
Clone the repo
git clone --depth 1 https://github.com/bijutharakan/multi-agent-squad

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 843 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00843
Opus 5 $0.00009 $0.00421
Sonnet 5 $0.00003 $0.00169
Haiku 4.5 $0.00002 $0.00084

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

Security

Grade A, and why

create-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 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.

.claude/commands/create-agent.md · 120 lines

How it starts

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

Create Agent Command

Generate a new specialized agent tailored to your project's specific needs.

What This Command Does

  1. Gathers Agent Requirements - Role, expertise, experience level
  2. Selects Template - Chooses appropriate base template
  3. Customizes for Project - Adds project-specific context
  4. Generates Agent File - Creates in .claude/agents/
  5. Registers Agent - Updates agent registry

Usage

  • /create-agent
  • "Create a new agent"
  • "I need a [role] agent"

Interactive Process

I'll ask you:

  1. Agent Role/Title (e.g., "Database Performance Expert")
  2. Primary Responsibilities (what they'll do)
  3. Experience Level (5/10/15+ years)
  4. Domain Expertise (specific technologies/industries)
  5. Tools Needed (Read, Write, Bash, etc.)
  6. Unique Experiences (war stories, specific achievements)

Example Flow

You: /create-agent

Me: Let's create a new agent! What role or title should this agent have?

You: Blockchain Security Expert

Me: Great! What will be their primary responsibilities?

You: Audit smart contracts, identify vulnerabilities, ensure security best practices

Me: What experience level? (Junior: 5 years, Senior: 10 years, Principal: 15+ years)

You: Senior - 10 years

Me: What specific domain expertise should they have?

You: Solidity, Ethereum, DeFi protocols, past experience with major hacks

Me: Creating your Blockchain Security Expert...

✓ Generated: .claude/agents/security/blockchain-security-expert.md
✓ Added war stories from famous DeFi hacks
✓ Included audit checklist and tools
✓ Registered in agent manifest

Your new agent is ready! They bring:
- 10 years of blockchain security experience
- Expertise in Solidity and smart contract vulnerabilities
- Experience preventing attacks like the DAO hack
- Comprehensive audit methodology

Agent Templates

Base templates available:

  • Developer (Frontend/Backend/Full-Stack)
  • Architect (Solution/System/Enterprise)
  • Manager (Product/Project/Engineering)
  • Specialist (Security/Performance/Data)
  • Quality (QA/Testing/Automation)
  • Operations (DevOps/SRE/Infrastructure)
  • Custom (Any specialized role)

Read the full file on GitHub · 120 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 · 120 lines · 17 tokens per session scan A e5235fbbfc98

Subscribe to this mod's changes

create-agent is a command published in the GitHub repository bijutharakan/multi-agent-squad (86 stars, last pushed 1y ago), licensed MIT. It adds 17 tokens to every session and 843 once invoked, about $0.0001 per session on Opus 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.