Borrowing it
Nothing to install: this file belongs to claude-code-expert/carve-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/claude-code-expert/carve-harness/main/.claude/commands/verify-loop.mdgit clone --depth 1 https://github.com/claude-code-expert/carve-harnessWrote 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/commands/claude-code-expert/carve-harness/verify-loop)<a href="https://agentmods.dev/commands/claude-code-expert/carve-harness/verify-loop"><img src="https://agentmods.dev/badge/commands/claude-code-expert/carve-harness/verify-loop/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/commands/claude-code-expert/carve-harness/verify-loop"><img src="https://agentmods.dev/badge/commands/claude-code-expert/carve-harness/verify-loop.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.00035 | $0.00247 |
| Opus 5.5 | $0.00014 | $0.00099 |
| Sonnet 5.5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
verify-loop 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 1mo 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.
What it actually says
carve-verify-loop 워크플로를 실행하라. $ARGUMENTS를 목표(goal)로 전달한다.
- 항목(tasks)을 직접 주지 않으면 P1에서 리서치 기반으로 3~7개 체크리스트 항목(claim·acceptance·owns 비중복)으로 자동 분해한다.
- 각 항목을 evaluator가 코드 대조로 0~100 채점하고, 95 미만 항목만 gap을 되먹여 재작업→재채점(항목당 최대 3회).
- 진행 상태는
specs/checklist.json에 기록되며, 미달 항목이 남으면checklist-gate훅이 완료(Stop)를 차단한다. - 워크플로 없이(타 에이전트·일반 세션) 같은 루프를 손으로 돌릴 때는
checklist-loop스킬의 SOP를 따른다.
$ARGUMENTS
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.
- 1mo ago First seen · 12 lines · 35 tokens per session scan A 0e08280b3c7e
verify-loop is a command published in the GitHub repository claude-code-expert/carve-harness (15 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 247 once invoked, about $0.0001 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-30.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.