Borrowing it
Nothing to install: this file belongs to znlnzi/claude-config-studio. 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/znlnzi/claude-config-studio/main/.claude/skills/verification-loop/SKILL.mdgit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/verification-loop)<a href="https://agentmods.dev/skills/znlnzi/claude-config-studio/verification-loop"><img src="https://agentmods.dev/badge/skills/znlnzi/claude-config-studio/verification-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/skills/znlnzi/claude-config-studio/verification-loop"><img src="https://agentmods.dev/badge/skills/znlnzi/claude-config-studio/verification-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.00010 | $0.00293 |
| Opus 5.5 | $0.00004 | $0.00117 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
verification-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 2mo 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
验证循环技能
验证触发点
编码中
- 每完成一个函数 → 运行相关测试
- 每修改一个文件 → 类型检查
功能完成后
- 运行完整测试套件
- 检查覆盖率
- 运行 lint
提交前
- 构建验证
- 全量测试
- 安全扫描
- 调试代码审计
验证步骤
快速验证（编码中）
- 类型检查通过
- 相关测试通过
- 无 lint 错误
完整验证（提交前）
- 构建成功
- 类型检查通过
- Lint 通过
- 全量测试通过
- 覆盖率达标
- 无调试语句
- 无安全问题
失败处理
验证失败时：
- 定位失败的步骤
- 分析根本原因
- 修复问题
- 重新运行完整验证
- 确认所有步骤通过
报告格式
验证完成后输出：
- 通过/失败状态
- 每个步骤的结果
- 失败项的详细信息
- 修复建议
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.
- 2mo ago First seen · 57 lines · 10 tokens per session scan A 7cc50dcd8c94
verification-loop is a skill published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 293 once invoked, about $0.0000 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
od-code-migration
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
react-component-testing
Applies the three-tier test taxonomy for React applications: unit tests for hooks and pure logic, component tests for behavior and interactions, and end-to-end tests for user flows. Uses Vitest, React Testing Library, and Playwright while focusing on observable behavior over implementation details.
fix-bug
Investigates and fixes a reported bug. Reads relevant code, identifies the root cause, proposes a fix, and adds or updates tests to prevent regression. Invoked when the user describes unexpected behavior, an error, a crash, or a failing test.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.
create-terraform-tests
Designs and implements Terraform module tests for AWS-targeted modules. Covers terraform-native tests, validation gates, fixture composition, and risk-focused assertions for regressions, address migration, and unsafe changes.