Unbrowse
unbrowse-ai/unbrowse
Search and call websites through Unbrowse's hosted API or remote MCP, reuse indexed site tools, read pages, and learn missing routes in its cloud browser.
Execute accepted long-running controller or durable Harness work, or postflight-sync already tracked work; ordinary clear changes use the current host directly.
Install Execute
$ npx skills add 0xenzyme/agent-harness --skill execute -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install 0xenzyme/agent-harness execute --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/0xenzyme/agent-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/agent-harness/skills/execute .claude/skills/execute && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "execute" agent skill from https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/execute into .claude/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/executeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add 0xenzyme/agent-harness --skill execute -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install 0xenzyme/agent-harness execute --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/0xenzyme/agent-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/agent-harness/skills/execute .agents/skills/execute && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "execute" agent skill from https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/execute into .agents/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 0xenzyme/agent-harness --skill execute -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install 0xenzyme/agent-harness execute --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/0xenzyme/agent-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/agent-harness/skills/execute .cursor/skills/execute && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "execute" agent skill from https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/execute into .cursor/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/0xenzyme/agent-harness.git --path plugins/agent-harness/skills/execute--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add 0xenzyme/agent-harness --skill execute -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install 0xenzyme/agent-harness execute --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/0xenzyme/agent-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/agent-harness/skills/execute .gemini/skills/execute && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "execute" agent skill from https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/execute into .gemini/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install 0xenzyme/agent-harness executeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add 0xenzyme/agent-harness --skill execute -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/0xenzyme/agent-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/agent-harness/skills/execute .github/skills/execute && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "execute" agent skill from https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/execute into .github/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 0xenzyme/agent-harness --skill execute -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install 0xenzyme/agent-harness execute --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/0xenzyme/agent-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/agent-harness/skills/execute .opencode/skills/execute && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "execute" agent skill from https://github.com/0xenzyme/agent-harness/tree/main/plugins/agent-harness/skills/execute into .opencode/skills/execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
execute- GitHub stars
- 107
- Token cost
- ~1.9k tokens
- SKILL.md length
- 885 words
- Files
- 3 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute accepted long-running controller or durable Harness work, or postflight-sync already tracked work; ordinary clear changes use the current host directly.
- Works in 11 steps: Classify the request → For durable work, read AGENTS.md,… → Before creating, forking, or handing off… → …
- Agent Workflows work in your project
- SKILL.md covers Workflow, Domain Invariants and Boundaries
- Calls node
What it does
Execute is an agent skill from 0xenzyme/agent-harness. Execute accepted long-running controller or durable Harness work, or postflight-sync already tracked work; ordinary clear changes use the current host directly. / 执行主控长任务、持久化控制或已有状态同步。
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/completion-evidence.md`).
It sits in Agent Workflows. The repository describes itself as: Adapter-driven control plane for coding-agent work: tasks, goals, run DAGs, gates, verification, and state sync. The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/execute”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- Classify the request
- For durable work, read AGENTS.md, inspect .harness/config.json, and load
- Before creating, forking, or handing off a project session, or delegating a
- Controller means outcome owner and accepted-state owner. It may implement
- For accepted long-running controller work, establish or reuse a compatible
- Validate or create the repository Goal, then prepare a Run when durable
- Give ready DAG nodes to the host when delegation is available. Harness
- Verify the accepted scope and durable required gates. Worker output remains
- Confirm authoritative Task/Goal phase, verification, required gates, and
- Synchronize the configured Goal/Task/status/Run state. Keep status bounded;
- Close with changed output, verification, accepted phase, Need user, and
What it can do on your machine
Read from SKILL.md and the folder at commit 098b96d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Execute loads about 1.9k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 885 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from 0xenzyme/agent-harness at commit 098b96d, republished under its MIT licence (© 0xenzyme). 885 words, ~1,905 tokens.
Download SKILL.mdSave it as
.claude/skills/execute/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- execute
- description
- Execute accepted long-running controller or durable Harness work, or postflight-sync already tracked work; ordinary clear changes use the current host directly. / 执行主控长任务、持久化控制或已有状态同步。
Harness Execute
Use this skill when accepted work needs durable recovery, audit, milestone acceptance, a Run/DAG, multiple workers, persistent state sync, or high-risk control, or when already completed simple work needs bounded postflight sync to existing Harness state. A clear ordinary change/build request uses the current host directly without this skill.
Read Completion Evidence before accepting or recording durable completion. Read Host Execution Bridge before selecting direct, postflight, or durable execution. Read Host Capabilities before using runtime outcome, transient plan, or delegation. Read Artifact Lifecycle before compacting task state or pruning Runs. Read Worker Runner Contract before delegating any DAG node or worker.
Workflow
- Classify the request:
host-direct: stop Harness execution; let the current host execute and verify.host-direct-postflight: verify completed work and update existing state only; create no lifecycle artifacts and do not apply durable completion gates.durable-harness: continue below. A prepared enforced Run always remains durable. Legacy aliasescodex-directandcodex-direct-postflightremain readable.
- For durable work, read
AGENTS.md, inspect.harness/config.json, and load the configured adapter, accepted Spec/Goal, active Run, and required gates. If the manifest enforces a checkpoint, runrun validateandrun checkpoint showbefore any project action; follow its sole next action and prohibited-action list. - Before creating, forking, or handing off a project session, or delegating a
worker, resolve work mode from the current user instruction,
AGENTS.md, the accepted Spec/Goal, and.harness/config.json. Runworktree recommendfor a Harness-managed project. If the result isaskor those sources conflict, pause for user direction before calling the host tool. Authorization to create a session or worker is not authorization to create a worktree. Do not pass host-specific starting checkout or session state unless the current user explicitly requests that specific existing Git state. Parallel-writer isolation is a reason to ask, not permission to override an unresolved work-mode decision. - Controller means outcome owner and accepted-state owner. It may implement
foreground work. Select
gate-onlyonly when the user or accepted Goal explicitly says the controller only reviews evidence; otherwise useimplementerfor edits inside accepted scope. - For accepted long-running controller work, establish or reuse a compatible
runtime outcome when the host exposes
runtimeOutcome. Use the host transient plan for multi-step work. Do not emulate missing runtime capabilities with extra repository artifacts. - Validate or create the repository Goal, then prepare a Run when durable execution is required:
node <plugin-root>/scripts/agent-harness.mjs goal validate --cwd <project> --goal <goal-file>
node <plugin-root>/scripts/agent-harness.mjs run prepare --cwd <project> --goal <goal-file>- Give ready DAG nodes to the host when
delegationis available. Harness does not start workers, choose concurrency, cancel runtimes, or pin model/effort by default. Record node ownership, verification, and candidate evidence before dependents run. Do not launch a dependent node before its recorded dependencies complete. Workers return candidate evidence and State Sync Notes; only the controller writes accepted Goal, Task, status, Run, or gate state. Areconciliation-requiredcheckpoint permits authoritative inspection only. Contract drift moves the old Run throughreplan-requiredto a validated replacement andsuperseded; never rebind its manifest. - Verify the accepted scope and durable required gates. Worker output remains candidate evidence until the accepted-state owner validates it. Before acceptance, challenge scope coverage, stale evidence, missing dependencies, path ownership, required checklist items, and whether the user's Milestone/Goal objective is larger than the local artifact.
- Confirm authoritative Task/Goal phase, verification, required gates, and
State Sync Notes.
blockedis resumable and non-complete; Run state is evidence and status is a bounded projection. - Synchronize the configured Goal/Task/status/Run state. Keep status bounded; preview artifact compaction when configured limits are exceeded. Pruning is a separate explicit destructive action and never follows from state sync. Completion evidence must name changed files, commands/results, gate evidence, State Sync Notes, remaining work, and any true user decision.
- Close with changed output, verification, accepted phase,
Need user, andRemaining.
Show full SKILL.md (267 more words)Show less
Domain Invariants
harness-rule:path-containment: every configured write, Goal/Spec reference, Run argument, and DAG artifact stays inside its configured project root, including existing-parent realpath and symlink checks.harness-rule:run-dag-ownership: a Run records ready nodes, dependencies, ownership, verification, and candidate evidence; scheduling belongs to the host.harness-rule:pre-delegation-work-mode: resolve local, worktree, or ask before host delegation; unresolved ask or conflicting sources pause for the user.harness-rule:candidate-accepted-evidence: executors return candidate evidence; only the accepted-state owner accepts gates or durable state.harness-rule:authoritative-completion-state: Task/Goal is the accepted-state authority with active, completed, or blocked phase; blocked is resumable and non-complete, Run stores evidence, and status is a bounded projection.harness-rule:state-sync-evidence: durable completion includes verified State Sync Notes and updates to already configured records.harness-rule:bounded-status-snapshot: status is a bounded current snapshot, while Goals, Runs, and gate records retain durable history.harness-rule:project-neutral-core: adapters own downstream paths and facts; plugin core stays project-neutral.harness-rule:durable-tier-boundary: ordinary clear change/build uses the current host directly; already recorded simple work may use postflight-only sync; durable ceremony is reserved for recovery, audit, milestone/DAG, multi-worker, persistent state sync, or high-risk control.harness-rule:checkpoint-recovery: explicitly enforced managed Runs use an independent revision-safe checkpoint; uncertain external state and contract drift fail closed, while disabled and legacy paths keep existing behavior.
Boundaries
- Do not infer authorization for credentials, production access, destructive operations, daemons, release, deploy, publish, or other external side effects.
- Do not mark durable work complete without required verification, gates, DAG evidence, and state sync.
- Do not apply durable gates to direct or postflight-only work, and do not use postflight wording to bypass an existing enforced Run.
- Preserve fixed and adapter contracts and report in the user's language.
© 0xenzyme, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in plugins/agent-harness/skills/execute of 0xenzyme/agent-harness.
- SKILL.md
- agents/openai.yaml
- references/completion-evidence.md
Open the folder on GitHubat commit 098b96d
Compare with similar skills
Execute next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Execute this skill0xenzyme/agent-harness | 107 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Unbrowseunbrowse-ai/unbrowse | 780 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Project ButlerJamesShi96/project-butler | 374 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Gemini SkillWJZ-P/gemini-skill | 832 | — | ~1.1k | Automated safety check: Pass | MIT | |
| agtx One-Shot Project Runnerfynnfluegge/agtx | 1.7k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Fleet Manager for Agent Sessionsasgeirtj/system_prompts_leaks | 69k | — | ~2.5k | Automated safety check: Pass | CC0-1.0 |
Similar skills
Project Butler
JamesShi96/project-butler
Project memory workflow for init/upgrade, profile-aware setup, end session, normal/full close, file organization, document archiving, language switching, versioned update logs, rule review, status…
Gemini Skill
WJZ-P/gemini-skill
通过 Gemini 官网（gemini.google.com）执行生图、对话等操作。用户提到"生图/画图/绘图/nano banana/nanobanana/生成图片"等关键词时触发。操作方式分三级优先级：首选 MCP 工具 → 次选 Skill 脚本 → 最次连接 Skill 浏览器手动操作（需用户授权）。禁止自行启动外部浏览器访问 Gemini。
agtx One-Shot Project Runner
fynnfluegge/agtx
Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.
Fleet Manager for Agent Sessions
asgeirtj/system_prompts_leaks
Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.
WebGPT
Nhahan/WebGPT
Hands bounded tasks from Codex to a signed-in ChatGPT web session at a chosen reasoning level, or opens a terminal chat in your project that you control.
More from 0xenzyme/agent-harness
Orient
0xenzyme/agent-harness
Inspect durable Agent Harness state and recommend the next public entry without mutation.
Init
0xenzyme/agent-harness
Explicitly audit, initialize, import, or repair Agent Harness setup and config migration; not for ordinary status, intake, or product implementation.
Intake
0xenzyme/agent-harness
Explicitly preview or record rough Agent Harness ideas, requirements, bugs, and inbox notes without accepting scope or implementing it.
Related
Categories
Questions about Execute
What does Execute do?
Execute accepted long-running controller or durable Harness work, or postflight-sync already tracked work; ordinary clear changes use the current host directly. Execute is an agent skill from 0xenzyme/agent-harness. Execute accepted long-running controller or durable Harness work, or postflight-sync already tracked work; ordinary clear changes use the current host directly.
When should I use Execute?
Execute fits situations like: agent Workflows work in your project.
How do I install Execute in Claude Code?
Run `npx skills add 0xenzyme/agent-harness --skill execute -a claude-code`. Or copy the skill folder (plugins/agent-harness/skills/execute in 0xenzyme/agent-harness) into .claude/skills/execute in your project. Claude Code loads it when a task matches its description.
How do I install Execute in Codex?
Run `npx skills add 0xenzyme/agent-harness --skill execute -a codex`. Or copy the skill folder (plugins/agent-harness/skills/execute in 0xenzyme/agent-harness) into .agents/skills/execute in your project. Codex loads it when a task matches its description.
Can I use Execute in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 0xenzyme/agent-harness --skill execute -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/execute, .gemini/skills/execute, .github/skills/execute and .opencode/skills/execute in your project.
What does Execute need to run?
Going by SKILL.md and its folder, Execute needs the command-line tools its instructions call (node).
Does Execute access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Execute safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Execute use?
Execute is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Execute use?
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 260 tokens, read only when the agent opens those files.
What are the alternatives to Execute?
Skills that share tags, products or a category with Execute: Unbrowse (unbrowse-ai/unbrowse, 780 stars), Project Butler (JamesShi96/project-butler, 374 stars), Gemini Skill (WJZ-P/gemini-skill, 832 stars) and agtx One-Shot Project Runner (fynnfluegge/agtx, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Execute?
0xenzyme (a GitHub user) maintains it in 0xenzyme/agent-harness, which has 107 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: 0xenzyme/agent-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.