wardenlisted
Install: claude install-skill srjn45/warden
# warden — drive your agent fleet, the warden way
warden (CLI `warden`, aliased `wd`) runs a local daemon that manages per-task
coding agents (Claude Code by default, plus other backends via `--backend`; each in
its own tmux session, most in a git worktree) and the work around them. You drive it through the **warden MCP tools** (when registered)
or the **`warden` CLI** (always available).
**Detect which surface you have, then commit to it — don't probe.** Look at
your tool list once: if `mcp__warden__*` tools are present, **prefer them** —
structured tool calls that return compact typed results, need no shell, and
don't trip Bash-permission prompts. If they are **absent**, the warden MCP
server is not registered in this session (common under org-managed MCP
allowlists) — do **not** attempt or search for MCP tools; go **straight to the
`warden`/`wd` CLI** via Bash and treat it as the primary surface, not a
degraded one. Every fleet/data capability has a CLI verb (each reference file
carries the CLI map), so a CLI-only session loses no capability. The handful of
admin verbs that are CLI-only are listed per capability.
### CLI-only fast path (no `mcp__warden__*` tools in this session)
The everyday verbs, so the common path needs no reference-file round-trip:
| Task | CLI |
|---|---|
| list / triage | `warden ls` (`--json`, `--watch`) |
| one agent's status / output | `warden status <id>` · `warden agent tail <id>` |
| spawn from a prompt | `warden start "<prompt>"` (`--name