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 skills add easyinplay/harnessed --skill progressgit clone --depth 1 https://github.com/easyinplay/harnessedWrote 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/easyinplay/harnessed/progress)<a href="https://agentmods.dev/skills/easyinplay/harnessed/progress"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/progress/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/easyinplay/harnessed/progress"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/progress.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00156 | $0.01533 |
| Opus 5.5 | $0.00062 | $0.00613 |
| Sonnet 5.5 | $0.00031 | $0.00307 |
| Haiku 4.5 | $0.00016 | $0.00153 |
Grade A, and why
verify-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 25d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-progress workflow (v3)
Overview
3-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 必跑串行" 起点 onto harnessed runtime (Phase v3.0-3.4 W0.10 — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 ref + Pattern A sub-workflow ship)。
| phase | id | upstream | model | capability / invokes | mode / artifacts |
|---|---|---|---|---|---|
| 1 | 01-gsd-verify-work |
gsd | sonnet | {{ capabilities.gsd-verify-work.cmd }} |
serial — UAT-driven acceptance |
| 2 | 02-gsd-progress |
gsd | haiku | {{ capabilities.gsd-progress.cmd }} |
serial — ROADMAP/STATE/REQUIREMENTS 同步 |
| 3 | 03-progress-update |
planning-with-files | haiku | {{ capabilities.planning-with-files.cmd }} + invokes: /plan |
artifacts_expected: [progress.md] |
Per-phase config loads from workflows/verify/progress/workflow.yaml; engine spawns each
phase as a sub-agent via @anthropic-ai/claude-agent-sdk 0.3.142+ in serial mode (顺序锁定 —
gsd-verify-work UAT 必先于 gsd-progress 状态同步)。
Capability refs
Sister workflows/capabilities.yaml entries:
gsd-verify-work— Bucket 2 special-purpose (impl: gsd, cmd: /gsd-verify-work)gsd-progress— Bucket 2 special-purpose (impl: gsd, cmd: /gsd-progress)planning-with-files— Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
Routing rules (sister CLAUDE.md "Verify 阶段")
总 fire 当 phase.stage == 'verify' (sister workflows/judgments/stage-routing.yaml
verify-progress-always trigger)。无 skip 条件 — verify-work 起点必跑。
How to invoke
!harnessed checkpoint intent verify-progress
The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spawn → checkpoint complete) resolve it, and a per-turn
<workflow-intent>reminder persists until they run.
The numbered sequence below is the state machine — execute it with Bash. Do NOT improvise an equivalent flow from the Overview above: freelancing bypasses the engine (no ledger, no evidence guard). harnessed gives you the spawn-ready prompt; YOU spawn the subagent with a {{ host.native }} {{ host.spawn_subagent }} (keeps the session responsive + lets clarification round-trips reach the user).
What ships with it
2 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.
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.
- 25d ago Changed · -1 lines d5a5f200527d
- 1mo ago First seen · 82 lines · 156 tokens per session scan A 6ea256e2a2af
verify-progress is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 156 tokens to every session and 1,533 once invoked, about $0.0006 per session on Opus 5.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-31.
Other skills, from other repositories
completion-verification
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of…
phx-work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
review-testing
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle…
r-testthat
Best practices for writing R package tests with testthat version 3+. Use this skill when writing or organizing tests for an R package or when improving existing tests that use testthat. It covers test structure and expectations, self-sufficient test design, proper cleanup with withr, fixtures, mocking external…
lab:autoresearch
Self-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration, evaluates against deterministic scorer, keeps improvements via git, reverts failures. Targets weakest skill+dimension. Use with /loop for overnight runs.
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.