agentmods.dev

plan-parallel

A command that runs the planning part of Auto-Harness in parallel. It first asks clarification questions and then drafts a project specification after the user answers; a specification is a written description of what should be built.

In plain words
What is it for?
Use it to start or continue a parallel planning workflow, validate planner outputs, and maintain its status and checkpoints. It does not write application source code or the specification directly from the main thread.
Why use it?
It separates planning from implementation and ensures missing requirements are clarified before the specification is drafted.

Command

14 4mo ago A scan 36 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/plan-parallel
Clone the repo
git clone --depth 1 https://github.com/redker56/auto-harness
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,641 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.00036 $0.01641
Opus 5 $0.00018 $0.00821
Sonnet 5 $0.00007 $0.00328
Haiku 4.5 $0.00004 $0.00164

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

Security

Grade A, and why

plan-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 2d 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/plan-parallel.md · 132 lines

How it starts

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

Auto-Harness Parallel Planner Orchestrator

You are still the main-thread Orchestrator, not the Planner itself.

Rules

  • Do not write the spec content yourself.
  • Do not write application source code.
  • Always use the correct fresh action-specific parallel Planner subagent.
  • The main thread may edit only .harness-parallel/status.md and .harness-parallel/checkpoints/latest.md.
  • Do not read, copy, rewrite, or migrate .harness/.
  • Keep workflow_mode=parallel in .harness-parallel/status.md.
  • Keep the user interaction in chat. Do not push them to open .harness-parallel/*.md just to continue planning.

State And Validation

  • read .harness-parallel/status.md directly
  • edit .harness-parallel/status.md directly when advancing state
  • edit .harness-parallel/checkpoints/latest.md directly only when you need to refresh the operator-facing checkpoint
  • validate planner outputs with node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" planner_clarify_parallel or node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" planner_spec_draft_parallel

Flow

  1. If .harness-parallel/status.md does not exist:
    • if $ARGUMENTS is empty, ask the user for a 1-4 sentence product brief and stop
    • otherwise dispatch a fresh auto-harness:planner-clarify-parallel-agent
    • pass only:
      • the user's original brief
      • the current project root
      • the current legal action is brief_clarification_parallel
    • required outputs:
      • .harness-parallel/intake.md
      • .harness-parallel/status.md
    • run node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" planner_clarify_parallel immediately after the subagent returns
    • if the check fails, re-dispatch the same Planner action with the reported repair reason and do not advance state
    • then edit .harness-parallel/status.md so it becomes:
      • phase=AWAITING_BRIEF_CLARIFICATION
      • current_sprint=0
      • pending_action=brief_clarification_parallel
      • last_agent=planner
      • approval_required=true
      • workflow_mode=parallel
    • read .harness-parallel/intake.md
    • present the clarification questionnaire directly in chat
    • do not answer any clarification question on the user's behalf
    • if the user has not supplied a clarification answer, treat that item as unresolved
    • mention .harness-parallel/intake.md only as the durable planning log
    • stop and wait for the user's inline answers

Read the full file on GitHub · 132 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. 2d ago First seen · 132 lines · 36 tokens per session scan A 8226ced6edc7

Subscribe to this mod's changes

plan-parallel is a command published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,641 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.

Planningagentclaude-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

release

Command "release" from CIrcui-try/Circuit, covering 절차, 1단계: 사전 확인, 2단계: 변경사항 수집, 직전 release 시점 (main의 가장 최근 release pr merge 시각) and 그 시점 이후 develop으로 머지된 pr 목록.

CIrcui-try/Circuit · 18 tokens

review-and-fix

로컬 변경사항을 직접 리뷰하고 문제점 수정 후 커밋·푸시.

CIrcui-try/Circuit · 18 tokens

takeoff

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

CIrcui-try/Circuit · 25 tokens