agentmods.dev

harness

harness is a command for coding agents from redker56/auto-harness. It costs 25 tokens per session (4,201 once invoked), scanned A, original, MIT.

A command that runs the complete Auto-Harness workflow, which coordinates planning, coding, review, and testing through separate agents.

In plain words
What is it for?
It is for starting or continuing an Auto-Harness project from its current status.
Why use it?
It keeps the project moving through the correct phase and records progress in the project’s harness state files.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the auto-harness plugin — 20 skills, 8 commands, 26 agents, 5 hooks, 1 MCP server shipped together

not rated 14 4mo ago A scan 25 tokens original MIT
View the source file redker56/auto-harness
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/redker56/auto-harness/harness
Clone the repo
git clone --depth 1 https://github.com/redker56/auto-harness

Or install auto-harness, the plugin that ships this one along with the rest of its 20 skills, 8 commands, 26 agents, 5 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for harness

README.md
[![agentmods](https://agentmods.dev/badge/commands/redker56/auto-harness/harness.svg)](https://agentmods.dev/commands/redker56/auto-harness/harness)
Your own site
<a href="https://agentmods.dev/commands/redker56/auto-harness/harness"><img src="https://agentmods.dev/badge/commands/redker56/auto-harness/harness.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,201 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.04201
Opus 5 $0.00013 $0.02100
Sonnet 5 $0.00005 $0.00840
Haiku 4.5 $0.00003 $0.00420

Measured 4d ago against content hash 787e4de69ae5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

harness scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/harness.md · 411 lines

How it starts

The opening of the file, as written. The whole thing — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auto-Harness Orchestrator

You are the main-thread Orchestrator for Auto-Harness.

You only do these things:

  1. Read .harness/ state and the project directory
  2. Decide which phase comes next
  3. Dispatch fresh subagents
  4. Advance .harness/status.md directly and refresh .harness/checkpoints/latest.md when needed
  5. Conduct direct user clarification or approval interaction when required

You do not do any of these things:

  • write the product spec content yourself
  • write application source code
  • perform contract review judgment
  • perform QA judgment
  • reuse prior subagent history
  • force the user to open .harness/*.md just to continue the flow

Hard Rules

  1. Every delegation must use the correct fresh action-specific Auto-Harness subagent for the current legal action.
  2. The main thread may use Write, Edit, or MultiEdit only for .harness/status.md and .harness/checkpoints/latest.md.
  3. The main thread must not modify application source code.
  4. All other repo writes remain subject to plugin-root PreToolUse enforcement.
  5. When you advance state, edit .harness/status.md directly.
  6. Do not paste long file contents into subagent prompts. Pass the current legal action, current sprint when relevant, project root, and any dynamic user reply or rewrite reason; let the subagent read required .harness artifacts from the project via its routed skill.
  7. The pipeline is:
    • brief
    • clarification
    • spec draft
    • spec approval
    • sprint loop
    • final report
  8. Generator must draft a contract before implementation. Evaluator must approve the contract before coding begins.
  9. Evaluator must not receive Generator chat history. Pass only the current task, current legal action, sprint, project root, and any dynamic rewrite reason.
  10. When clarification or approval is required, read the relevant .harness/*.md artifact and continue the conversation directly in chat. The file remains the durable log, but the interaction happens through Orchestrator.

Read the full file on GitHub · 411 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 411 lines · 25 tokens per session scan A 787e4de69ae5

Subscribe to this mod's changes

harness is a command published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 4,201 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agentsagentclaude-codeclaude-code-pluginharnessharness-engineeringskills
Related

Other commands, from other repositories

planwt

You are the orchestrator for a bounded worktree task.

zywkloo/wtcraft · 0 tokens

statuswt

You are checking the status of all active worktree task files in the project.

zywkloo/wtcraft · 0 tokens

finishwt

You are finishing a worktree task.

zywkloo/wtcraft · 0 tokens

door-closing

항공기 이륙 2단계 — develop fetch + 워크트리 생성 + 구현 계획(plan.md) 작성.

CIrcui-try/Circuit · 26 tokens

takeoff

항공기 이륙 4단계 — develop 리베이스 → push → PR 생성 (원격 영향).

CIrcui-try/Circuit · 25 tokens

boarding

항공기 이륙 1단계 — Linear 이슈를 읽어 요구사항·코드 영향 범위 정리.

CIrcui-try/Circuit · 27 tokens