Install
$ agentstack add skill-d3x293-code-crew-agent-manager ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 --description "desc"
Creates a new custom agent definition.
Required arguments:
name— Agent name (alphanumeric + hyphens, e.g., "api-specialist")--model— Model tier:sonnetorhaiku(Opus reserved for CEO)--description— What this agent specializes in
Process:
- Validate the name is unique (not already in crew-team.json)
- Create directory
.claude/crew-agents/if it doesn't exist - Generate the agent file
.claude/crew-agents/{name}.mdusing 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}
- Register the agent in
.claude/crew-team.json:
"custom-{name}": {
"model": "{tier}",
"active": true,
"role": "{description}",
"custom": true,
"definitionPath": ".claude/crew-agents/{name}.md"
}
- Confirm to user:
Agent "{name}" created ({tier}) — .claude/crew-agents/{name}.md
Edit definition to customize. Auto-registered in routing.
list — List All Agents
- Read
.claude/crew-team.json - Display all agents (built-in + custom):
Agents:
Built-in:
ceo (opus) Active - Triage, decompose, delegate
vp-engineering (sonnet) Active - Architecture, tech decisions
...
Custom:
api-specialist (sonnet) Active - Expert in REST API layer
db-optimizer (haiku) Active - Database query optimization
If no custom agents: "No custom agents. /crew agent create to add one."
remove "name" — Remove a Custom Agent
- Validate the agent exists in crew-team.json and has
"custom": true - Cannot remove built-in agents — if attempted: "Can't remove built-in agent. Use /crew config to disable."
- Remove the agent entry from
.claude/crew-team.json - Delete the agent file
.claude/crew-agents/{name}.md - Confirm:
"Custom agent '{name}' removed."
Integration with Task Routing
The task-router and lite-router should check .claude/crew-team.json for custom agents:
- When classifying a task, check if any custom agent's description keywords match the task
- Custom agents can be inserted into routing chains:
- If
model: haiku→ can replace junior-dev for matching tasks - If
model: sonnet→ can replace senior-dev for matching tasks
- Custom agents follow the same dispatch protocol (Index-First, skill injection, self-contained prompts)
Example: If a custom "api-specialist" agent exists with description "Expert in REST API layer", and the user runs /crew task "fix the API endpoint for users", the router may choose api-specialist over senior-dev since it's more specialized.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: d3x293
- Source: d3x293/code-crew
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.