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/validate-phasenpx skills add easyinplay/harnessed --skill validate-phasegit 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/validate-phase)<a href="https://agentmods.dev/skills/easyinplay/harnessed/validate-phase"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/validate-phase.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.00123 | $0.01374 |
| Opus 5 | $0.00062 | $0.00687 |
| Sonnet 5 | $0.00025 | $0.00275 |
| Haiku 4.5 | $0.00012 | $0.00137 |
Grade A, and why
verify-validate-phase 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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-validate-phase workflow (v3)
Overview
1-phase sub-workflow auditing requirement→test coverage gaps (v13.0 P43 upstream re-sync — D-04 Stage ④ Verify conditional sub + GSD validate-phase wire)。回溯审计 phase 完成后的 requirement→test 覆盖缺口,为未覆盖 requirement 生成测试 (gsd-nyquist-auditor agent), 补 TDD 前向写测试之外的后向查漏。
| phase | id | upstream | model | capability | gate |
|---|---|---|---|---|---|
| 1 | 01-validate-phase |
gsd | sonnet | {{ capabilities.gsd-validate-phase.cmd }} |
judgments.stage-routing.verify-validate-phase-coverage.fires |
Per-phase config loads from workflows/verify/validate-phase/workflow.yaml; engine 4-level gate
resolver evaluates phase.requires_coverage_audit == true via expr-eval — true 则 invoke GSD
/gsd-validate-phase (Nyquist 覆盖审计 → VALIDATION.md), false 则 skip。
Capability refs
Sister workflows/capabilities.yaml entries:
gsd-validate-phase— Bucket 2 special-purpose (impl: gsd, cmd: /gsd-validate-phase, fires_when: requires_coverage_audit)
Gate ref
Sister workflows/judgments/stage-routing.yaml:
verify-validate-phase-coverage.fires—phase.stage == 'verify' and phase.requires_coverage_audit == true
How to invoke
!harnessed checkpoint intent verify-validate-phase
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).
Do NOT pipe to harnessed run verify-validate-phase — that is the CI/headless path (in-process SDK spawn
that blocks the session inside Claude Code).
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.
- 3d ago First seen · 77 lines · 123 tokens per session scan A 207ce4aa9403
verify-validate-phase is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 123 tokens to every session and 1,374 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-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.