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.
npx agentmods add agents/intense-visions/harness-engineering/harness-parallel-coordinatorgit clone --depth 1 https://github.com/Intense-Visions/harness-engineeringWrote 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.
[](https://agentmods.dev/agents/intense-visions/harness-engineering/harness-parallel-coordinator)<a href="https://agentmods.dev/agents/intense-visions/harness-engineering/harness-parallel-coordinator"><img src="https://agentmods.dev/badge/agents/intense-visions/harness-engineering/harness-parallel-coordinator.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00037 | $0.03105 |
| Opus 5 | $0.00018 | $0.01553 |
| Sonnet 5 | $0.00007 | $0.00621 |
| Haiku 4.5 | $0.00004 | $0.00311 |
Grade A, and why
harness-parallel-coordinator 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.
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Verify task independence, create focused agent briefs, dispatch Task Executor instances in isolated worktrees, integrate results, and run full validation after all agents complete.
Skills
- harness-parallel-agents
Steps
- Run
harness validate(always) - Execute harness-parallel-agents skill (manual)
Methodology
Harness Parallel Agents
Dispatch independent tasks to concurrent agents, integrate results, and verify no conflicts. Only for truly independent problems.
Invoked automatically by harness-autopilot (and standalone harness-execution), not only manually. When a plan's phase has an auto-dispatch wave, the execution loop calls this skill to run that wave. In that mode the caller supplies worktree-per-unit isolation per docs/guides/agent-worktree-patterns.md (one worktree per task, sequential commits, squash-merge on integrate) and has already verified independence via plan_parallelization; this skill still owns the focused agent briefs (Step 2), concurrent dispatch (Step 3), and integration/verification (Steps 4–5). Manual invocation (a human asking to "work in parallel") continues to work unchanged.
When to Use
- When 3 or more tasks are truly independent (no shared state, no shared files, different subsystems)
- When tasks involve investigation or implementation in separate parts of the codebase
- When parallel execution would meaningfully reduce wall-clock time
- When a plan has tasks explicitly marked as parallelizable
- When
harness-autopilot/harness-executionreaches anauto-dispatch(or confirmed) wave fromplan_parallelization— this skill is the wave's dispatcher - NOT when failures across tasks might be related (investigate serially to find the common cause)
- NOT when tasks need full system understanding to complete correctly
- NOT when agents would modify the same files or shared state
- NOT when there are fewer than 3 independent tasks (overhead of coordination outweighs parallelism)
- NOT when the tasks are sequential by nature (each depends on the previous)
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.
- 4d ago First seen · 299 lines · 37 tokens per session scan A 65e7478ce846
harness-parallel-coordinator is an agent published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 3,105 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.