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 skills/chachamaru127/claude-code-harness/harness-loopnpx skills add Chachamaru127/claude-code-harness --skill harness-loopgit clone --depth 1 https://github.com/Chachamaru127/claude-code-harnessWrote 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/skills/chachamaru127/claude-code-harness/harness-loop)<a href="https://agentmods.dev/skills/chachamaru127/claude-code-harness/harness-loop"><img src="https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/harness-loop.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.00066 | $0.03452 |
| Opus 5 | $0.00033 | $0.01726 |
| Sonnet 5 | $0.00013 | $0.00690 |
| Haiku 4.5 | $0.00007 | $0.00345 |
Grade A, and why
harness-loop 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Loop
Codex 版の harness-loop は、説明だけの擬似ループではなく、
実際にバックグラウンドで回るランナーを起動する。
ひとことで
$harness-loop は、1 回だけの実装依頼ではなく、
「今すぐ実行できる未完了タスクのまとまりを、Breezing で自動実行し続ける当番」を起動する入口。
ここでいう ready batch は、Depends が満たされていて、今すぐ並列実行できる cc:TODO / cc:WIP のまとまり。
1 cycle は 1 task ではなく、原則として 1 ready batch を処理する。
たとえると
人が横でずっと見張る代わりに、 「同時に進められる作業をまとめて見つける → Breezing に任せる → 結果を確認する → 次のまとまりへ進む」 を繰り返す監督係を、裏で常駐させるイメージ。
Quick Reference
| 入力 | 動作 |
|---|---|
$harness-loop all |
未完了タスク全体を長時間ループで開始 |
$harness-loop 41.1-41.4 |
範囲を絞って開始 |
$harness-loop JLB3R-02..JLB3R-08 |
Plans.md の task ID 順で範囲を絞って開始 |
$harness-loop all --max-cycles 3 |
最大 3 サイクルで停止 |
$harness-loop all --max-workers 4 |
1 cycle の ready batch を最大 4 worker までに制限 |
$harness-loop all --max-workers max |
ready batch 内で実行可能なタスク数を上限として並列化 |
$harness-loop all --plan roadmap |
named Plans の roadmap を対象にループ実行 |
$harness-loop all --executor task |
旧来の 1 task per cycle local worker 実行へ逃がす |
$harness-loop all --pacing night |
サイクル間の待機を長めにする |
$harness-loop status |
現在の実行状況を確認 |
$harness-loop stop |
進行中ジョブを止めてループ停止要求を出す |
実行コマンド
開始
harness codex-loop start all
範囲指定:
harness codex-loop start 41.1-41.4 --max-cycles 5 --pacing worker
harness codex-loop start JLB3R-02..JLB3R-08 --max-cycles 5 --pacing worker
harness codex-loop start all --max-workers max --pacing worker
harness codex-loop start all --plan roadmap --max-cycles 5
harness codex-loop start all --executor task --max-cycles 5
START..END は、Plans.md に並んでいる task ID をそのまま使う範囲指定。
英字やハイフンを含む task ID は .. を優先する。
41.1-41.4 のような従来の数値レンジも引き続き使える。
--max-workers は、Breezing が 1 cycle で同時に動かす worker 数の上限。
max は、選択範囲内で Depends が満たされた ready task の数をそのまま上限にする。
--executor task は、Breezing ではなく local worker に 1 task だけ渡す互換用の逃げ道。
問題切り分けや、並列実行したくない危険な作業で使う。
複数 Plans.md がある repo では、長時間 run の起動時に --plan NAME を明示する。
runner は開始時に解決した Plans file を cycle 間で保持するため、途中で active plan を切り替えない。
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 · 239 lines · 66 tokens per session scan A 2f47624d6b15
harness-loop is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,082 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 3,452 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…