add-agentlisted

Add a subagent named **$ARGUMENTS** to this repository. ## Existing agents ```! ls agents/ 2>/dev/null || ls .claude/agents/ ``` ## Steps 1. **Check it does not already exist.** If an existing agent covers the job, extend that one instead — two agents with overlapping descriptions make the delegation choice ambiguous. 2. **Create `agents/<name>.md`** with this frontmatter: ```yaml --- name: <name> description: <when to use it — this is what the orchestrator matches on> model: <haiku | sonnet | opus> tools: <comma-separated> --- ``` 3. **Pick the model by cost of being wrong**, per `.claude/rules/common/efficiency.md`: - `haiku` — light, mechanical work (documentation updates). - `sonnet` — the default for workers (review, tests, build fixes, refactors). - `opus` — deep reasoning where a miss is expensive (architecture, security). 4. **Least privilege on tools.** Read-only agents get `Read, Grep, Glob, Bash` and nothing else. Only grant `Write`/`Edit` to an agent whose job is to change files. A reviewer that can edit code will quietly fix what it should have reported. 5. **Write the body** as: what the agent is, its process, and what it outputs. Reviewers state severity levels and an explicit verdict. Keep it short — an agent prompt that rambles gets skimmed the same way a long CLAUDE.md does. 6. **Register it in the roster.** Add a row to the table in `.claude/rules/common/agents.md` (Agent | Purpose | When to Use).