harness-progress

harness-progress is a skill for Claude Code, Codex from Chachamaru127/claude-code-harness. It costs 121 tokens per session (2,097 once invoked), scanned A, original, MIT.

A tool that creates a single HTML progress snapshot from Plans.md, a project task-tracking file. It shows task counts, completion percentage, time, estimated time, cost, and drift alerts for the current session.

In plain words
What is it for?
Use it to generate or regenerate a progress page, optionally choosing its output path or preventing it from opening in a browser.
Why use it?
It gives non-engineers a quick browser view of what is finished, what is in progress, and what remains, without reading project files.

Skill for Claude CodeCodex

Part of the claude-code-harness plugin — 25 skills, 5 commands, 5 agents, 27 hooks shipped together

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 skills/chachamaru127/claude-code-harness/harness-progress
Any agent
npx skills add Chachamaru127/claude-code-harness --skill harness-progress
Clone the repo
git clone --depth 1 https://github.com/Chachamaru127/claude-code-harness

Made for: Claude Code, Codex.

Or install claude-code-harness, the plugin that ships this one along with the rest of its 25 skills, 5 commands, 5 agents, 27 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/harness-progress.svg)](https://agentmods.dev/skills/chachamaru127/claude-code-harness/harness-progress)
Your own site
<a href="https://agentmods.dev/skills/chachamaru127/claude-code-harness/harness-progress"><img src="https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/harness-progress.svg" alt="Measured on agentmods" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,097 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.00121 $0.02097
Opus 5 $0.00060 $0.01048
Sonnet 5 $0.00024 $0.00419
Haiku 4.5 $0.00012 $0.00210

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

Security

Grade A, and why

harness-progress 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.

codex/.codex/skills/harness-progress/SKILL.md · 138 lines

How it starts

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

Harness Progress Tracker

Phase 65.4 (Progress Tracker) — 3rd surface of the cognitive-load HTML triplet. Plan Brief / Acceptance Demo に続く 3 つ目の HTML surface で、進行中セッションの全体像を 1 枚の紙で把握 できるようにする。

Quick Reference

入力 動作
/harness-progress 現プロジェクトの進捗 snapshot HTML を生成し開く
/harness-progress --no-open 生成のみ (browser 開かない、PostToolUse hook 用)
/harness-progress --out <path> 出力先指定 (default: out/progress-snapshot.html)

Mission

"今のセッションは何件のタスクをどこまで終わらせて、いつ終わる見込みで、いくら使ったか" を、 エンジニアじゃない vibecoder が 3 秒でブラウザで把握 できる HTML 1 枚を生成する。

やる:

  • Plans.md の cc:TODO / cc:WIP / cc:完了 件数を集計
  • progress_pct (完了率) を計算 (cc:完了 ÷ 総タスク × 100)
  • 経過分数 / 推定総分数 / コスト so-far / コスト estimate を表示
  • drift alert を表示 (Phase 65.4.3 以降で populate)

やらない (本 cycle):

  • WebSocket / SSE による live update (静的 HTML、再生成で更新)
  • 過去 session の history 比較 (Phase 65.4.4 で別軸)
  • 他 project の cross-project view (Phase 65.3 と独立)

Schema: progress-snapshot.v1

詳細仕様: schemas/progress-snapshot.v1.schema.json

schema:        progress-snapshot.v1
project:       <basename of git repo>
current_task:  <cc:WIP の最初の項目 1 行サマリ、なければ空文字>
progress_pct:  <0-100 の整数、cc:完了 ÷ 総タスク × 100 の四捨五入>
todo_tasks:    [{number, title}]    ← cc:TODO のみ
wip_tasks:     [{number, title}]    ← cc:WIP のみ
done_tasks:    [{number, title, commit}]   ← cc:完了 [hash] のみ、hash は 7 chars
elapsed_minutes:          <int, state file から>
estimated_total_minutes:  <int, state file から>
cost_so_far_usd:          <float, state file から>
cost_estimate_usd:        <float, state file から>
alerts:                    []   ← Phase 65.4.3 以降で populate
generated_at:             <ISO8601 UTC>
writing_lint_pending:     [{id, pattern, approve_command, pending_count}]  ← optional/additive (Phase 136.2)
deferred_ops_pending:     [{id, command, approve_command, pending_count}]  ← optional/additive (Phase 140.2)

writing_lint_pending (Phase 136.2)

scripts/writing-rule-list.sh --status pending --json の出力をそのまま snapshot に 組み込む optional フィールド。pending proposal が 0 件のときは配列が空になり、 progress.html.template の該当セクションは何も展開せず非表示になる (render-html.sh の {{#section}} は配列が空だと block を 0 回展開するため)。

Read the full file on GitHub · 138 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 Changed · +4 lines bb5fe2ec4da0
  2. 4d ago First seen · 134 lines · 121 tokens per session scan A 09b1b5246295

Subscribe to this mod's changes

harness-progress is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,082 stars, last pushed 3d ago), licensed MIT. It adds 121 tokens to every session and 2,097 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens