agentmods.dev

harness-parallel

harness-parallel is a command for coding agents from redker56/auto-harness. It costs 31 tokens per session (5,422 once invoked), scanned A, original, MIT.

A coordinator for running the Auto-Harness workflow with several workers in separate Git worktrees, which are isolated working copies of a repository. It moves the workflow through its defined stages and records its state.

In plain words
What is it for?
Use it to coordinate specification, code generation, evaluation, testing, fixes, and retesting in a parallel Auto-Harness run.
Why use it?
It manages parallel workers and approvals without mixing their changes with the main project or using the wrong workflow stage.

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 31 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-parallel
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-parallel

README.md
[![agentmods](https://agentmods.dev/badge/commands/redker56/auto-harness/harness-parallel.svg)](https://agentmods.dev/commands/redker56/auto-harness/harness-parallel)
Your own site
<a href="https://agentmods.dev/commands/redker56/auto-harness/harness-parallel"><img src="https://agentmods.dev/badge/commands/redker56/auto-harness/harness-parallel.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,422 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.00031 $0.05422
Opus 5 $0.00015 $0.02711
Sonnet 5 $0.00006 $0.01084
Haiku 4.5 $0.00003 $0.00542

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

Security

Grade A, and why

harness-parallel 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-parallel.md · 458 lines

How it starts

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

Auto-Harness Parallel Orchestrator

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

You only do these things:

  1. Read .harness-parallel/ state and the project directory
  2. Decide which phase comes next
  3. Dispatch fresh subagents
  4. Advance .harness-parallel/status.md directly and refresh .harness-parallel/checkpoints/latest.md when needed
  5. Conduct direct user clarification or approval interaction when required
  6. Create and clean up worktrees for parallel Generator work

You do not write the product spec yourself, write application source code directly, make QA judgments, or reuse prior subagent history.

Hard Rules

  1. Keep the parallel workflow isolated from the stable serial workflow by using these pending_action values:
    • brief_clarification_parallel
    • spec_approval_parallel
    • generator_contract_parallel
    • evaluator_review_parallel
    • generator_build_parallel
    • evaluator_qa_parallel
    • generator_fix_parallel
    • evaluator_retest_parallel
    • evaluator_final_parallel
  2. Use the matching fresh action-specific Auto-Harness subagent for the current legal action.
  3. The main thread may use Write, Edit, or MultiEdit only for .harness-parallel/status.md and .harness-parallel/checkpoints/latest.md.
  4. The main thread must not modify application source code.
  5. All other repo writes remain subject to plugin-root PreToolUse enforcement.
  6. Do not paste long file contents into subagent prompts. Pass the current legal action, sprint when relevant, project root, and any dynamic user reply or rewrite reason; let the subagent read the required .harness-parallel artifacts itself.
  7. Generator must draft a contract before implementation. Evaluator must approve the contract before coding begins.
  8. Evaluator must not receive Generator chat history.
  9. Build uses dependency-graph scheduling from the parallel sprint contract.
  10. Fix does not require predeclared workstreams in QA or retest. Instead, the Orchestrator reads the existing ## Bugs or ## Remaining Bugs table, splits the bug IDs into temporary fix batches, records those batches in ## Parallel Execution State, and dispatches fix workers from that temporary batch list.
  11. Generator integrators own all branch merges.
  12. Only the final integrator pass may write Generator-owned .harness-parallel artifacts.
  13. Keep workflow_mode=parallel in .harness-parallel/status.md for every parallel session.

Read the full file on GitHub · 458 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 · 458 lines · 31 tokens per session scan A 73b7bda9e496

Subscribe to this mod's changes

harness-parallel is a command published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 5,422 once invoked, about $0.0002 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.

Git and workflowagentclaude-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

takeoff

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

CIrcui-try/Circuit · 25 tokens

boarding

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

CIrcui-try/Circuit · 27 tokens

door-closing

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

CIrcui-try/Circuit · 26 tokens