القائمة
Use when Codex should delegate scoped work to an installed external agent harness, inspect an Every Harness mailbox, or cancel active delegated work through the `every-harness` CLI.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | every-harness |
| description | Use when Codex should delegate scoped work to an installed external agent harness, inspect an Every Harness mailbox, or cancel active delegated work through the `every-harness` CLI. |
every-harness is the local CLI for delegating bounded Codex work to another installed harness. This Skill is a Codex playbook: run the CLI yourself when delegation is useful, and keep the user-facing summary short.
Every Harness does not register slash commands, MCP servers, hooks, or hidden defaults. The CLI is the source of truth for command syntax:
every-harness --help
every-harness run --help
every-harness status --help
every-harness cancel --help
run.every-harness run --harness <id> [--background] [--write|--read-only] [--model <model>] [--effort <effort>] [--prompt-file <path>] <task text>
every-harness status [--harness <id>] [--all] [--wait]
every-harness cancel [--harness <id>]
Use every-harness run when a separate harness should execute a scoped implementation, review, exploration, or model-specific pass.
Use every-harness status when you need to inspect active or completed delegated work.
Use every-harness cancel when delegated work is stale, wrong, or explicitly stopped by the user.
--harness; do not rely on hidden defaults.--write only when the delegated harness should modify files.--background only when you intend to continue locally and check back with every-harness status.