Agent Skills: codex-herdr

Route explicit Herdr control requests from Codex Desktop. Not for Codex CLI or OMP.

UncategorizedID: michaelvessia/nixos-config/codex-herdr

Install this agent skill to your local

pnpm dlx add-skill https://github.com/MichaelVessia/nixos-config/tree/HEAD/modules/programs/agents/shared/skills/codex-herdr

Skill Files

Browse the full folder contents for codex-herdr.

Download Skill

Loading file tree…

modules/programs/agents/shared/skills/codex-herdr/SKILL.md

Skill Metadata

Name
codex-herdr
Description
Route explicit Herdr control requests from Codex Desktop. Not for Codex CLI or OMP.

codex-herdr

Router for controlling herdr from the Codex Desktop app only. The host application determines eligibility, not the model provider or model name. OMP running a Codex model is still OMP, not Codex Desktop. If the host is not known to be Codex Desktop, do not use this router; use the applicable native herdr skill instead.

"Herder" and "herder" in a request mean herdr; the CLI binary is always herdr. Once the Desktop-only gate is satisfied, pick the workflow from the environment.

  1. Spawning an agent and handing it a task is dispatch. Read and follow the sibling herdr-dispatch skill (../herdr-dispatch/SKILL.md) in either environment. The user's request that fired this skill is the explicit request it requires.
  2. Inspecting or controlling existing panes, tabs, and agents needs the CLI reference. Check echo "${HERDR_ENV:-unset}". If HERDR_ENV=1, read and follow the sibling herdr skill (../herdr/SKILL.md). Otherwise use only the Follow-up commands in herdr-dispatch.
  3. Verify connectivity first with herdr workspace list; if it fails, herdr is not running. Report that and stop.

Boundary

The herdr skill's HERDR_ENV gate is intentional: it stops an outside shell from acting as if it owned the focused pane. Never set or fake HERDR_ENV to reach the native path, and never treat the focused pane as yours from outside. Outside Herdr, everything goes through herdr-dispatch.