opencode-simple: Skill for Claude Code

.opencode/skills/verification-loop/SKILL.md

verification-loop is a skill for Claude Code, OpenCode from zhmxiaowo/opencode-simple. It costs 25 tokens per session (778 once invoked), scanned A, original, MIT.

A code-checking workflow based on compilation and language-server checks. A language server is a tool that reports code errors while you work; CDD means Compile-Driven Development.

In plain words
What is it for?
Use it after features, refactors, or before a pull request to compile the project, inspect language-server errors, and optionally run lint checks.
Why use it?
It gives projects without tests a defined way to find errors after changes. It stops when compilation fails and checks that no error-level diagnostics remain.

Skill for Claude CodeOpenCode

Written for Claude Code and OpenCode: PostToolUse hook event, but also installed under .opencode/. Also seen: mentions OpenCode.

This is zhmxiaowo/opencode-simple's own configuration. It tells Claude Code and OpenCode how to work on opencode-simple itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opencode-simple configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zhmxiaowo/opencode-simple. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zhmxiaowo/opencode-simple/main/.opencode/skills/verification-loop/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple

Made for: Claude Code, OpenCode.

Wrote 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.

agentmods badge for verification-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/zhmxiaowo/opencode-simple/verification-loop/github.svg)](https://agentmods.dev/skills/zhmxiaowo/opencode-simple/verification-loop)
Your own site
<a href="https://agentmods.dev/skills/zhmxiaowo/opencode-simple/verification-loop"><img src="https://agentmods.dev/badge/skills/zhmxiaowo/opencode-simple/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.

agentmods 80×15 button for verification-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/zhmxiaowo/opencode-simple/verification-loop"><img src="https://agentmods.dev/badge/skills/zhmxiaowo/opencode-simple/verification-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 778 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00778
Opus 5.5 $0.00010 $0.00311
Sonnet 5.5 $0.00005 $0.00156
Haiku 4.5 $0.00003 $0.00078

Measured 1mo ago against content hash 75e431ca3f18, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.opencode/skills/verification-loop/SKILL.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CDD Verification Loop Skill

A compile-driven verification system. 不运行任何测试。唯一的验证标准是编译通过 + LSP 无 Error。

When to Use

Invoke this skill:

  • After completing a feature or significant code change
  • Before creating a PR
  • When you want to ensure compile gates pass
  • After refactoring

Verification Phases

Phase 1: Build / Compile Verification

自动检测项目类型并运行对应命令:

# TypeScript/Node.js
npx tsc --noEmit --pretty 2>&1 | head -30
# OR npm run build / pnpm build

# C# / Unity
dotnet build --no-restore 2>&1 | tail -20

# C++ / Unreal / CMake
cmake --build build/ 2>&1 | tail -20

# Rust
cargo check 2>&1 | tail -20

# Go
go build ./... 2>&1 | tail -20

# Python (type check)
pyright . 2>&1 | head -30

If build fails:

  1. STOP — do not proceed
  2. Invoke sequential-thinking for root cause analysis
  3. Use build-error-resolver agent to fix
  4. Re-run compile until Exit Code 0

Phase 2: LSP Diagnostics Check

Use mcp-language-server to verify:

  • 0 Error-level diagnostics
  • Review Warning-level diagnostics (optional fix)

Phase 3: Lint Check

# JavaScript/TypeScript
npm run lint 2>&1 | head -30

# Python
ruff check . 2>&1 | head -30

Phase 4: Security Scan

# Check for secrets
grep -rn "sk-" --include="*.ts" --include="*.js" --include="*.cs" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.ts" --include="*.js" --include="*.cs" . 2>/dev/null | head -10

# Check for debug logging
grep -rn "console.log\|Debug.Log\|UE_LOG" src/ 2>/dev/null | head -10

Phase 5: Diff Review

# Show what changed
git diff --stat
git diff HEAD~1 --name-only

Review each changed file for:

  • Unintended changes
  • Missing error handling
  • Potential edge cases

Output Format

After running all phases, produce a CDD verification report:

CDD VERIFICATION REPORT
=======================

Compile:   [PASS/FAIL] (Exit Code: X)
Types/LSP: [PASS/FAIL] (X errors)
Lint:      [PASS/FAIL] (X warnings)
Security:  [PASS/FAIL] (X issues)
Diff:      [X files changed]

Overall:   [READY/NOT READY] for PR

Issues to Fix:
1. ...
2. ...

Read the full file on GitHub · 129 lines

Changes

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.

  1. 1mo ago First seen · 129 lines · 25 tokens per session scan A 75e431ca3f18

Subscribe to this mod's changes

verification-loop is a skill published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 778 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-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens