# Customize · subagentengineering

> Build a Claude Code agent definition. Tabs: solo agent, team, enterprise presets, research experiments. Every page ships a recorded replay demo (animated for humans, this markdown for agents).

Canonical URL: https://www.subagentengineering.com/customize
Last verified: 2026-05-19

## What this page does

- Picks tools (`Read`, `Write`, `Edit`, `Bash`, `WebFetch`, etc.) from `lib/agent-config.ts`
- Selects a model (`claude-opus`, `claude-sonnet`, `claude-haiku`)
- Selects a permission mode (default, acceptEdits, bypassPermissions, plan)
- Generates a real `.claude/agents/<name>.md` file with YAML frontmatter

## Replay demos available on this page

### Ticket-deflector

> _Triage a refund-after-cancel support ticket_

**Model:** `claude-haiku-4-5`  
**Cassette:** `cassettes/small-business/ticket-deflector.har.json`  
**Replay URL:** [https://www.subagentengineering.com/api/v1/replay/small-business/ticket-deflector](https://www.subagentengineering.com/api/v1/replay/small-business/ticket-deflector)  
**Tokens spent on replay:** 0

**Stream live**

```bash
curl https://www.subagentengineering.com/api/v1/replay/small-business/ticket-deflector
```

**Prompt**

```
Classify this support ticket and draft a reply if it's auto-respondable: 'I cancelled my Starter plan yesterday but got charged again for $29.'
```

**Response (replayed verbatim from the cassette)**

```
Classification: (b) escalate to billing — duplicate-charge after a cancellation requires a finance review.

Draft reply (held for billing review, not sent):
Thanks for flagging this — I'm pulling the cancellation and the new charge now so billing can confirm both in one pass. You'll get a refund + a written confirmation that the Starter plan is fully closed within one business day.
```

### CI-failure-triage

> _Classify a recurring OOM in the payments suite + propose next action_

**Model:** `claude-haiku-4-5`  
**Cassette:** `cassettes/developer-tools/ci-failure-triage.har.json`  
**Replay URL:** [https://www.subagentengineering.com/api/v1/replay/developer-tools/ci-failure-triage](https://www.subagentengineering.com/api/v1/replay/developer-tools/ci-failure-triage)  
**Tokens spent on replay:** 0

**Stream live**

```bash
curl https://www.subagentengineering.com/api/v1/replay/developer-tools/ci-failure-triage
```

**Prompt**

```
Classify a failing CI run (OOM in tests/payments, same shape as last night, merge queue 6 deep, main green at HEAD~3) as flaky / author bug / infra incident, then propose next action.
```

**Response (replayed verbatim from the cassette)**

```
Classification: (c) infra-incident — same OOM signature recurring on consecutive nightly + headline merge-queue runs is regression shape, not flake.

Next action (in order):
1. Open the existing #4807 follow-up and link #4812; don't duplicate.
2. `pause-mq` while the queue is 6 deep — keeps the OOM from cascading.
3. Bisect payments suite against main HEAD~3 — the 7-of-38 shard split implies a fixture leak across describe blocks.
4. If bisect points at the AnthropicClient mock from the last 72h, swap it for the replay-mode FsPersister — cassette path keeps memory flat.
```

## Related markdown surfaces

- [/customize/team.md](/customize/team.md)
- [/customize/enterprise.md](/customize/enterprise.md)
- [/customize/experiments.md](/customize/experiments.md)
- [/llms.txt](/llms.txt)