Claude Code Harness is a development workflow for coding agents that organizes work into planning, implementation, review, synchronization, and release stages. It helps developers keep specifications, tests, independent reviews, and release evidence connected while using tools such as Claude Code, Codex CLI, Cursor, or Grok.
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-syncnpx skills add Chachamaru127/claude-code-harness --skill harness-syncgit 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-sync)<a href="https://agentmods.dev/skills/chachamaru127/claude-code-harness/harness-sync"><img src="https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/harness-sync.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.00050 | $0.02735 |
| Opus 5 | $0.00025 | $0.01367 |
| Sonnet 5 | $0.00010 | $0.00547 |
| Haiku 4.5 | $0.00005 | $0.00274 |
Grade B, and why
harness-sync scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
tail -20 .claude/state/agent-trace.jsonl 2>/dev/null | jq -r '.files[].path' | sort -u How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Sync
Plans.md と実装状況を照合し、差分を検出・更新する。
旧 sync-status および harness-plan sync サブコマンドの独立版。
Quick Reference
| ユーザー入力 | 動作 |
|---|---|
harness-sync |
進捗同期 + レトロスペクティブ（デフォルト ON） |
harness-sync --no-retro |
進捗同期のみ（レトロスキップ） |
harness-sync --snapshot |
スナップショット保存（進捗の時点記録） |
harness-sync --plan roadmap |
named Plans の roadmap を同期 |
| "今どこ？" / "進捗確認" | 同上 |
オプション
| オプション | 説明 | デフォルト |
|---|---|---|
--snapshot |
現在の進捗をスナップショットとして保存 | false |
--no-retro |
レトロスペクティブをスキップ | false（デフォルトで実行） |
--plan NAME |
plans/manifest.json の named plan を使う |
active/default |
Step 0: Plans.md 検証
Plans.md の存在とフォーマットを確認する。問題がある場合は即座に案内して停止する。
複数 Plans.md がある repo では、対象 plan を scripts/plan-registry.sh list または --plan NAME で確認してから読む。
| 状態 | 案内 |
|---|---|
| Plans.md が存在しない | Plans.md が見つかりません。harness-plan create で作成してください。 → 停止 |
| ヘッダーに DoD / Depends カラムがない（v1 形式） | Plans.md が旧フォーマット（3カラム）です。harness-plan create で v2（5カラム）に再生成してください。既存タスクは自動的に引き継がれます。 → 停止 |
| v2 形式（5カラム） | そのまま Step 1 に進む |
Step 1: 現状収集（並列）
# Plans.md の状態
cat Plans.md
# Git 変更状態
git status
git diff --stat HEAD~3
# 直近コミット履歴
git log --oneline -10
# エージェントトレース（直近の編集ファイル）
tail -20 .claude/state/agent-trace.jsonl 2>/dev/null | jq -r '.files[].path' | sort -u
Step 1.5: Agent Trace 分析
Agent Trace から直近の編集履歴を取得し、Plans.md のタスクと照合する:
# 直近の編集ファイル一覧
RECENT_FILES=$(tail -20 .claude/state/agent-trace.jsonl 2>/dev/null | \
jq -r '.files[].path' | sort -u)
# プロジェクト情報
PROJECT=$(tail -1 .claude/state/agent-trace.jsonl 2>/dev/null | \
jq -r '.metadata.project')
照合ポイント:
| チェック項目 | 検出方法 |
|---|---|
| Plans.md にないファイル編集 | Agent Trace vs タスク記述 |
| タスク記述と異なるファイル | 想定ファイル vs 実際の編集 |
| 長時間編集がないタスク | Agent Trace 時系列 vs WIP 期間 |
Step 2: 差分検出
| チェック項目 | 検出方法 |
|---|---|
完了済みなのに cc:WIP |
コミット履歴 vs マーカー |
着手済みなのに cc:TODO |
変更ファイル vs マーカー |
cc:完了 なのに未コミット |
git status vs マーカー |
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.
- 5d ago First seen · 266 lines · 50 tokens per session scan B 9cdedc9702e5
harness-sync is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,082 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 2,735 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…