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/commands/verify.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/commands/znlnzi/claude-config-studio/verify)<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/verify"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/verify/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/znlnzi/claude-config-studio/verify"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/verify.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.00007 | $0.00265 |
| Opus 5.5 | $0.00003 | $0.00106 |
| Sonnet 5.5 | $0.00001 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
verify 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
/verify - 验证协议
执行六个顺序检查的综合验证。
验证步骤
1. 构建验证
运行构建命令，必须通过才能继续。
2. 类型检查
报告所有类型错误及其位置。
3. Linting
运行 lint 工具，报告样式和质量问题。
4. 测试执行
运行测试套件，报告通过率和覆盖率。
5. 调试代码审计
检查源代码中的 console.log、debugger 等调试语句。
6. 版本控制状态
显示未提交的更改摘要。
执行模式
- quick: 仅构建 + 类型检查
- full: 全部六个步骤
- pre-commit: 构建 + 类型 + lint + 调试审计
- pre-pr: 全部步骤 + 安全扫描
使用方式
- /verify quick - 快速验证
- /verify full - 完整验证
- /verify pre-commit - 提交前验证
- /verify pre-pr - PR 前验证
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 · 42 lines · 7 tokens per session scan A 4901c19c0931
verify is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 265 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 commands, from other repositories
paul:verify
Guide manual user acceptance testing of recently built features.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.