fabius-cohorslisted

<!-- © 2026 shear559 · fabius · provenance fab1-6bbf82d118bce2cee9d7ac71f034fa26 · release evidence: PROVENANCE.md · github.com/shear559/fabius --> # Fabius Cohors — build agents that actually work *Cohors* — the cohort, the tactical unit of a Roman legion. Most "agent" requests need ONE good cohort member, not a legion: reach for multi-agent only when the work genuinely splits. The lean question (`fabius-parcus`) comes first — *does the second agent need to exist?* ## The definition — every agent needs these four This schema illustrates the information to specify, not a universal configuration format. Map it to the active harness's documented fields, supported model controls, and permission semantics before creating an agent; unsupported fields do not enforce a boundary. ```yaml --- description: what it does AND when to dispatch it # the dispatcher reads this — make it precise mode: subagent | primary | all model: provider/model-id # cheap tier for mechanical work, strong tier for judgment temperature: 0.0–1.0 # low for tools/code, higher for creative permission: read: allow | ask | deny edit: allow | ask | deny bash: allow | ask | deny # or a per-command map: {"*":"ask","git status *":"allow"} tools: [only the tools it actually needs] --- <system prompt: role, the 3–5 operating rules that matter, the output contract> ``` Four things make an agent reliable: - **A precise `description`** — this is how a dispatcher picks it. Vague descript