agentslisted

# /agents Top-level orchestrator for the `/agents` family — the **file-family cluster**: `AGENTS.md`, its multi-tool stubs (`CLAUDE.md`, `GEMINI.md`, `.github/copilot-instructions.md`, `.cursorrules`), and the surrounding agent infrastructure (rules, skills, pointers). > Looking for `agents/` folder operations (scaffold, folder-audit, > folder-cleanup)? Those live under [`/optimize agents-dir`](optimize/agents-dir.md). ## Sub-commands | Sub-command | Routes to | Purpose | |---|---|---| | `/agents init` | `commands/agents/init.md` | Bootstrap the agent layer — create `AGENTS.md` + tool stubs from the canonical template | | `/agents optimize` | `commands/agents/optimize.md` | Refactor `AGENTS.md` to the Thin-Root contract; propagate to multi-tool stubs | | `/agents audit` | `commands/agents/audit.md` | Read-only health check — token overhead, rule triggers, AGENTS.md health, stale references | | `/agents user` | `commands/agents/user.md` | User-persona file (`.agent-user.md`) — interview, render, maintenance | Sub-command names match the locked contract in [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md). ## Dispatch 1. Parse the user's argument: `/agents <sub-command> [args]`. 2. Look up the sub-command in the table above. 3. Load the body of the routed file and follow its `## Steps` section verbatim with the remaining args. 4. If the sub-command is unknown or missing, print the table above and ask: > 1. init — bootstrap AGENTS.md