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/easyinplay/harnessed/progressnpx skills add easyinplay/harnessed --skill progressgit clone --depth 1 https://github.com/easyinplay/harnessedWhat 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.00156 | $0.01525 |
| Opus 5 | $0.00078 | $0.00763 |
| Sonnet 5 | $0.00031 | $0.00305 |
| 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 yesterday.
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 — 82 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 CC-native Task / Agent tool (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.
- yesterday 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 6d ago), licensed Apache-2.0. It adds 156 tokens to every session and 1,525 once invoked, about $0.0008 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-31.
Other skills, from other repositories
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
comet-hotfix
Comet 预设 —— 通过 open-build-verify-archive 短流程修复已有行为 bug。.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
comet-design
Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.