agent-lordlisted

Dispatch and supervise durable Codex CLI, Codex App, Claude Code, or MCode CLI endpoints through deterministic scripts that enforce execution contracts, source identity, recovery, and sanitized results. Preserve explicit dependencies and run independent named actions concurrently when the workspace contract permits; surface any required isolation or integration decision before dispatch. Route explicit cross-review or 交叉 Review requests through the built-in cross-review policy, and explicit handoff / 交接 requests through the built-in handoff policy. Use when a Codex Desktop user asks to start or continue external Codex, Claude, or MCode work; not for in-process subagents, CI jobs, or general DAG workflows.
coder-xieshijie/agent-lord · ★ 0 · AI & Automation · score 62

Install: claude install-skill coder-xieshijie/agent-lord

# Agent Lord Route one logical task to one durable endpoint. Treat `node core/dist/cli.js` as the control plane: the model supplies intent and performs Codex App host-tool actions when requested, while the script owns provider defaults, validation, retries, state, recovery, and artifact extraction. ## Runtime setup Use Node.js 24 or newer. From this Skill's repository root, run `pnpm install --frozen-lockfile` and `pnpm --filter @agent-lord/core build` after installation or source updates. Invoke the compiled CLI from this root; when calling it elsewhere, use its absolute path. Provider binaries still come from the terminal environment or the configured `AGENT_LORD_*_BIN` variables. For an existing Python installation, drain its running controllers and provider processes before switching the shared state directory to TypeScript. The JSON formats and endpoint identities stay compatible; process-lock implementations must not be mixed. See [README.md](README.md) for cutover and rollback steps. ## Invariants - Keep the delegated task's implementation, analysis, review, test execution, and semantic acceptance in the user-authorized external endpoints unless the user explicitly asks the caller to take over in the current session. The caller handles context transfer, dispatch, supervision, and result convergence, and may directly inspect dispatch contracts, run records, and deliverable completeness or review the orchestration process itself. These control-plane checks do not a