agent-harness

Compile goals into verifiable task plans and drive bounded execute-verify-close agent loops.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill agent-harness-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-harness
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/agent-harness
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill agent-harness-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Autonomous agents often declare work done without proof, retry the same failing approach forever, or lose progress when context resets. This Skill turns a domain folder of skills into a bounded agentic loop where every task carries machine-run verification checks, retries are capped, exhausted budgets escalate to a human, and the loop refuses to close until everything is verified or explicitly waived. ## Core Features & Use Cases - Goal compilation: goal_compiler.py converts a goal statement into an ordered JSON task plan scored against a domain manifest, refusing vague goals (exit 3) with forcing questions. - Enforced loop state machine: loop_controller.py drives init/next/record/verify/close with atomic state files, running verification checks itself via subprocess so the agent never adjudicates its own work. - Manifest generation: harness_manifest_builder.py scans a domain's skills and emits a diff-stable JSON inventory of tools, checks, and agentic signals for CI gating. - Use Case: Give an agent the goal "audit the payments service and design an SLO"; the harness compiles it into tasks against the engineering manifest, executes one task at a time, re-runs each task's checks itself, and only closes after every task passes with recorded evidence. ## Quick Start Ask the agent to run your goal through the agent-harness engineering loop, starting by compiling the goal with goal_compiler.py against a manifest in assets/harnesses and then driving loop_controller.py until it closes or escalates.

Frequently Asked Questions about agent-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a goal through an agentic loop with verification?▼

Compile the goal with goal_compiler.py against a domain manifest to produce plan.json, initialize state with loop_controller.py init, then repeat next/record/verify until the directive is close or escalate. The controller runs each task's check commands itself via subprocess before marking anything verified.

How do I build a harness manifest for a folder of skills?▼

Run harness_manifest_builder.py with --domain pointing at the skill folder and --repo-root at the repository root. It scans every SKILL.md, extracts tools and verification checks, and emits a diff-stable JSON manifest when --no-timestamp is set, suitable for CI drift checks.

What happens when a task keeps failing in the loop?▼

Each failed attempt increments a counter, and the retry directive demands a changed approach. When max_attempts is reached the task escalates with exit code 2, blocking the loop until a human reviews the evidence log or waives the task with a recorded reason.

Can the agent mark its own tasks as verified?▼

No. The verify subcommand re-runs the task's check commands itself via subprocess with a timeout, and a passing verify record without an --evidence line is rejected with exit 6. Close refuses with exit 4 while any task remains unverified and unwaived.

When should I not use the agent-harness loop?▼

Do not use it for authoring Claude Code Workflow-tool scripts (use workflow-builder), N-agent tournaments on one task (agenthub), single-file metric optimization (autoresearch-agent), or discovering published loop recipes (loop-library). It is for driving a goal to a verified close across a domain of skills.

Is it safe to run the harness on plan files from external sources?▼

No. The verify step shell-executes each task's check command, so a tampered plan or state file is effectively arbitrary command execution. Only run the harness on plan and state files produced by you or goal_compiler.py.