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/code-reviewnpx skills add easyinplay/harnessed --skill code-reviewgit 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.00122 | $0.01410 |
| Opus 5 | $0.00061 | $0.00705 |
| Sonnet 5 | $0.00024 | $0.00282 |
| Haiku 4.5 | $0.00012 | $0.00141 |
Grade A, and why
verify-code-review 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-code-review workflow (v3)
Overview
1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — code-review 多 agent 并行" 章节 onto harnessed runtime (Phase v3.0-3.4 W0.11 — D-04 Stage ④ Verify 7 sub + 子任务并行 机制 subagent default routing 机器化 + Pattern A sub-workflow ship)。
| phase | id | upstream | model | capability | parallelism |
|---|---|---|---|---|---|
| 1 | 01-code-review |
mattpocock-skills | sonnet | {{ capabilities.code-review.cmd }} |
judgments.parallelism-gate.subagent-default.fires |
Per-phase config loads from workflows/verify/code-review/workflow.yaml; engine spawns
multiple subagent in parallel fan-out (bundled subagent-default rule — Task / Agent
工具 spawn 多任务并发, context 隔离, summary 折叠回主 context)。
Capability refs
Sister workflows/capabilities.yaml entries:
code-review— Bucket 1 mattpocock 高频招式 (impl: mattpocock-skills, cmd: /code-review)
Parallelism gate ref
Sister workflows/judgments/parallelism-gate.yaml:
subagent-default.fires—subtask.parallel_count <= 3 and subtask.communication_needed == false(默认 fan-out, focused 任务 research / verify / review 单文件 / 跑测试 / 抓 doc / 探索模块)
Routing rules
总 fire 当 phase.stage == 'verify' 后必跑串行 (verify-progress) 之后并行 fan-out。无 skip
条件 — code-review 多 agent 是 verify-work 第 3 phase 默认 fan-out (sister CLAUDE.md verbatim)。
How to invoke
!harnessed checkpoint intent verify-code-review
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.
- 2d ago First seen · 83 lines · 122 tokens per session scan A 7deb274bf3bb
verify-code-review is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 122 tokens to every session and 1,410 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.