How do I install the Harness Offload skill?

Run npx skillmds@latest add timsonner/harness-offload in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Harness Offload safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Harness Offload?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Harness Offload free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Harness Offload?

timsonner (@timsonner) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Harness Offload by timsonner — Agent Skill

Name: Harness Offload
Author: timsonner

Harness Offload

Offload one bounded job to agy, opencode, copilot, codex, or hermes via a shared contract (worker, dir, prompt, allow_tools, session). Use when the host agent should hand a task to another CLI and get back session_id + stdout. Triggers: "/harness-offload", offload contract, Invoke-HarnessOffload.

timsonner 66518cb 2 files · 13.3 KB Updated Sep 17, 2026

File contents

Harness offload

Host agent stays orchestrator. One worker, one directory, one prompt, then stop.

Flags and install live in the matching *-harness skills. This skill is only the job shape and the dispatcher.

Contract

Field	Meaning
`worker`	`agy` \| `opencode` \| `copilot` \| `codex` \| `hermes`
`dir`	workspace; sessions are per-dir (defaults to cwd)
`prompt`	bounded task
`allow_tools`	off = Q&A; on = that worker’s documented auto-approve
`session`	omit = new; else resume that worker’s id
`model`	optional override

Result (stdout of the script, one JSON object):

worker, session_id, exit_code, stdout, dir, allow_tools, stderr

A failed worker still prints JSON. Check exit_code (and stderr) before trusting stdout.

Invoke

From the agent-skills clone:

$env:Path = [System.Environment]::GetEnvironmentVariable('Path','Machine') + ';' +
            [System.Environment]::GetEnvironmentVariable('Path','User')

.\harness-offload\scripts\Invoke-HarnessOffload.ps1 `
  -Worker copilot `
  -Dir <dir> `
  -Prompt "Your bounded task"

-AllowTools only when the task must write/run. Never default it on. Do not pass --yolo / --auto / --dangerously-skip-permissions yourself — the script maps -AllowTools to the matching flag.

agy --print still needs a persisted allowlist or it jetskis (read_file / command auto-denied, empty stdout). The dispatcher merges read_file(*) and command(*) into ~/.gemini/antigravity-cli/settings.json. That is not -AllowTools and does not allow write_file.

The script appends: do not spawn agy / opencode / copilot / codex / hermes. Do not strip that.

Rules

Caller picks the worker. This is not a model router.
One writer per dir. Do not fan two workers into the same tree.
Resume with the returned session_id on the same worker + dir.
Need TUI, ACP, MCP, or install help → the matching *-harness skill.

Smoke

$tmp = Join-Path $env:TEMP "harness-offload-smoke"
New-Item -ItemType Directory -Force -Path $tmp | Out-Null
$script = ".\harness-offload\scripts\Invoke-HarnessOffload.ps1"

& $script -Worker agy -Dir $tmp -Prompt "Respond with exactly: AGY_SMOKE_OK"
& $script -Worker opencode -Dir $tmp -Prompt "Respond with exactly: OPENCODE_SMOKE_OK"
& $script -Worker copilot -Dir $tmp -Prompt "Respond with exactly: COPILOT_SMOKE_OK"
& $script -Worker codex -Dir $tmp -Prompt "Respond with exactly: CODEX_SMOKE_OK"
& $script -Worker hermes -Dir $tmp -Prompt "Respond with exactly: HERMES_SMOKE_OK"

Each JSON stdout must contain that worker’s *_SMOKE_OK string and a non-empty session_id. Resume: pass -Session <session_id> with a follow-up prompt on the same -Dir.

---name: harness-offloaddescription: Offload one bounded job to agy, opencode, copilot, codex, or hermes via a shared contract (worker, dir, prompt, allow_tools, session). Use when the host agent should hand a task to another CLI and get back session_id + stdout. Triggers: "/harness-offload", offload contract, Invoke-HarnessOffload.license: MIT---# Harness offloadHost agent stays orchestrator. One worker, one directory, one prompt, then stop.Flags and install live in the matching `*-harness` skills. This skill is onlythe job shape and the dispatcher.## Contract| Field | Meaning ||---|---|| `worker` | `agy` \| `opencode` \| `copilot` \| `codex` \| `hermes` || `dir` | workspace; sessions are per-dir (defaults to cwd) || `prompt` | bounded task || `allow_tools` | off = Q&A; on = that worker’s documented auto-approve || `session` | omit = new; else resume that worker’s id || `model` | optional override |Result (stdout of the script, one JSON object):```textworker, session_id, exit_code, stdout, dir, allow_tools, stderr```A failed worker still prints JSON. Check `exit_code` (and `stderr`) before trusting `stdout`.## InvokeFrom the **agent-skills** clone:```powershell$env:Path = [System.Environment]::GetEnvironmentVariable('Path','Machine') + ';' + [System.Environment]::GetEnvironmentVariable('Path','User').\harness-offload\scripts\Invoke-HarnessOffload.ps1 ` -Worker copilot ` -Dir <dir> ` -Prompt "Your bounded task"````-AllowTools` only when the task must write/run. Never default it on.Do **not** pass `--yolo` / `--auto` / `--dangerously-skip-permissions`yourself — the script maps `-AllowTools` to the matching flag.agy `--print` still needs a persisted allowlist or it jetskis(`read_file` / `command` auto-denied, empty stdout). The dispatcher merges`read_file(*)` and `command(*)` into `~/.gemini/antigravity-cli/settings.json`.That is not `-AllowTools` and does not allow `write_file`.The script appends: do not spawn agy / opencode / copilot / codex / hermes. Do not strip that.## Rules1. Caller picks the worker. This is not a model router.2. One writer per `dir`. Do not fan two workers into the same tree.3. Resume with the returned `session_id` on the **same** worker + `dir`.4. Need TUI, ACP, MCP, or install help → the matching `*-harness` skill.## Smoke```powershell$tmp = Join-Path $env:TEMP "harness-offload-smoke"New-Item -ItemType Directory -Force -Path $tmp | Out-Null$script = ".\harness-offload\scripts\Invoke-HarnessOffload.ps1"& $script -Worker agy -Dir $tmp -Prompt "Respond with exactly: AGY_SMOKE_OK"& $script -Worker opencode -Dir $tmp -Prompt "Respond with exactly: OPENCODE_SMOKE_OK"& $script -Worker copilot -Dir $tmp -Prompt "Respond with exactly: COPILOT_SMOKE_OK"& $script -Worker codex -Dir $tmp -Prompt "Respond with exactly: CODEX_SMOKE_OK"& $script -Worker hermes -Dir $tmp -Prompt "Respond with exactly: HERMES_SMOKE_OK"```Each JSON `stdout` must contain that worker’s `*_SMOKE_OK` string and anon-empty `session_id`. Resume: pass `-Session <session_id>` with afollow-up prompt on the same `-Dir`.

Frequently asked questions