agent-manager

A manager for custom coding agents that stores project-specific agent definitions and registers them for task routing.

In plain words
What is it for?
Use it to create agents with Sonnet or Haiku model tiers, list available agents, or remove custom agents.
Why use it?
It makes specialized agents reusable within one project without changing the built-in team.

Skill for Claude CodeCodex

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 skills/d3x293/code-crew/agent-manager
Any agent
npx skills add d3x293/code-crew --skill agent-manager
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,094 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.00036 $0.01094
Opus 5 $0.00018 $0.00547
Sonnet 5 $0.00007 $0.00219
Haiku 4.5 $0.00004 $0.00109

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

Security

Grade A, and why

agent-manager 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.

skills/agent-manager/SKILL.md · 144 lines

How it starts

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

Agent Manager - Custom Agent Creation

Manages project-specific custom agents that extend the built-in CodeCrew team.

When to Activate

  • User runs /crew agent create|list|remove

Storage

Custom agents are stored in .claude/crew-agents/ (project-local directory, NOT in the plugin's agents/ directory). This keeps custom agents project-specific and avoids conflicts with plugin updates.

Subcommands

create "name" --model <tier> --description "desc"

Creates a new custom agent definition.

Required arguments:

  • name — Agent name (alphanumeric + hyphens, e.g., "api-specialist")
  • --model — Model tier: sonnet or haiku (Opus reserved for CEO)
  • --description — What this agent specializes in

Process:

  1. Validate the name is unique (not already in crew-team.json)
  2. Create directory .claude/crew-agents/ if it doesn't exist
  3. Generate the agent file .claude/crew-agents/{name}.md using the appropriate template:

Sonnet agent template:

---
name: crew-{name}
description: {user's description}
model: sonnet
---

You are the **{Name}** at CodeCrew. {user's description}.

## INDEX-FIRST PROTOCOL (MANDATORY)

**INDEX-FIRST**: Read `.claude/crew-index.json` → `crew-symbols.json` → then only specific lines from source files. Never read entire files.

## Your Responsibilities

1. {Edit this section to define specific responsibilities}
2. {Add more as needed}

## Output Format

When done, report:
- What you changed (file paths + summary)
- FILES_MODIFIED: {list}
- Confidence level: high | medium | low
- Any concerns or dependencies

Haiku agent template:

---
name: crew-{name}
description: {user's description}
model: haiku
---

You are the **{Name}** at CodeCrew. {user's description}.

## INDEX-FIRST PROTOCOL (MANDATORY)

**INDEX-FIRST**: Read `.claude/crew-index.json` → `crew-symbols.json` → then only the lines you need. Never read entire files.

## Your Tasks

- {Edit this section to define specific tasks}
- If the task is too complex, report: "ESCALATE: Needs senior-dev"

## Output

FILES_MODIFIED: {list}
CONFIDENCE: {high | medium | low}

Read the full file on GitHub · 144 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 · 144 lines · 36 tokens per session scan A 49877605e850

Subscribe to this mod's changes

agent-manager is a skill published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,094 once invoked, about $0.0002 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.