harness-engineering · v1.0 · 2026-10-27 · sha256 863db49d44456a65
harness-engineering v1.0A
Immutable. This exact content never changes and is served at /api/v1/blob/863db49d44456a65.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_r6w6s57vzdm3qslh/863db49d44456a65787f7a6a48f9eabc0a5cb52047725b55fdbcf42346bab829.json
Then /plugin install harness-engineering@markdownregistry-r6w6s57vzdm3qslh in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: harness-engineering description: Design and evaluate reliable AI-agent systems through context selection, host-enforced policy, bounded tools and runtime, independent outcome verification, and privacy-aware observability. Use when building or changing agent workflows, tool access, approvals, verification, or agent telemetry. metadata: scope: repo-level version: "1.0" --- # Harness Engineering The model proposes what to do; the surrounding system controls execution and establishes whether the requested outcome actually happened. Treat reliability as an end-to-end property of context, policy, runtime, verification, and feedback—not as a prompt-only property. ## Components ### 1. Context builder - Supply the task goal, current state, relevant instructions, constraints, and success criteria. - Keep always-loaded context concise; retrieve detailed documents and data when relevant. - Distinguish trusted instructions from user input, retrieved documents, and tool output. Treat the latter as data, not as authority to change policy. - Do not pass secrets or unrelated personal data into context. ### 2. Model - Treat model output as a proposal, not authorization, ground truth, or proof of completion. - The host controls the agent loop, available tools, and whether a proposal can execute. - Stop and surface ambiguity, contradictory evidence, or repeated unproductive attempts. ### 3. Policy gate - Enforce identity, resource scope, allowed action, and relevant arguments at the tool/action boundary using deterministic host policy. - Fail closed when authorization cannot be established. Do not rely on model instructions or a model-generated policy judgment to grant access. - Pause for explicit human approval before actions designated sensitive or consequential by the host's policy. ### 4. Tools and runtime - Give each agent only the tools and permissions required for its task. - Validate tool arguments and constrain file, network, and service access in the host. - Bound execution with timeouts and call/retry budgets. Stop on exhausted budgets or repeated failures; do not retry side effects unless the operation is safe to repeat. - Require confirmation or approval for irreversible actions according to host policy. ### 5. Verification - Define observable acceptance criteria before execution. - Verify the resulting artifact or external state with tests, read-back, or another independent check appropriate to the task. - Report the evidence and any remaining uncertainty. A model's assertion that it succeeded is not verification. ### 6. Observability and feedback - Record enough structured events to diagnose runs: correlation/run identifier, tool name, policy decision, sanitized arguments, result category, errors, retries, and verification outcome. - Do not default to storing secrets, full prompts, personal data, or private model reasoning. Apply access controls, redaction, and retention limits to traces. - Use failures and near misses to improve deterministic checks, tests, tool contracts, and context—not just to add more prompt text. ## Completion invariant A task is complete only when its acceptance criteria have been checked against evidence. When a required control is not available in the agent host, state that limitation and do not represent configuration guidance as runtime enforcement. ## Scope boundary This skill describes design requirements. It does not itself enforce permissions, isolate tools, obtain approvals, validate external state, or collect telemetry; those controls must be implemented by the consuming application or agent runtime.