What is verify-changes?

A command that checks recent code changes in stages, starting with quick checks and moving to tests and deeper review.

Use it after implementing a change to inspect the diff, run the project's linter, type checker, build, and tests, then review failures.

It catches simple problems early and stops before spending time on slower checks. This helps verify that a change still builds, passes types and tests, and meets quality expectations.

verify-changes — Command by CloudAI-X

Install

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.

agentmods

npx agentmods add commands/cloudai-x/opencode-workflow/verify-changes

Clone the repo

git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 707 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00009	$0.00707
Opus 5	$0.00005	$0.00353
Sonnet 5	$0.00002	$0.00141
Haiku 4.5	$0.00001	$0.00071

Measured 2d ago against content hash f01278d6cd06, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/verify-changes.md · 108 lines

How it starts

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

Verify Changes Command

Comprehensive verification of recent changes using the adversarial verification approach from claude-workflow-v2.

Philosophy

Use progressive quality gates - run cheap checks first, expensive checks later. If early checks fail, stop immediately to save time.

Phase 1: Gather Context

Run in parallel:

git diff HEAD~1 or git diff - Understand what changed
git status - See current state
Identify affected files and their types (source, test, config)

Phase 2: Fast Checks (Fail-Fast Gate)

Run these quick checks first (~5-30 seconds each). Stop on first failure:

Lint Check

Detect project linter (eslint, prettier, ruff, golint, etc.)
Run: npm run lint or equivalent
Exit immediately if lint fails

Type Check

Detect type system (TypeScript, mypy, etc.)
Run: npx tsc --noEmit or equivalent
Exit immediately if type errors exist

Build Check

Run: npm run build or equivalent
Verify compilation succeeds

Phase 3: Deep Checks (Quality Gate)

Only proceed if Phase 2 passes:

Test Execution

Run: npm test or equivalent
Capture test results and coverage if available
Report any failing tests with details

Security Scan (if security-auditor agent available)

Invoke @security-auditor for OWASP top 10 review
Check for obvious vulnerabilities in changed code

Phase 4: Adversarial Review

Spawn parallel verification subagents (if Task tool available):

Logic Reviewer: "Review the changed code for logical errors, edge cases, and potential bugs"
Consistency Checker: "Verify the changes are consistent with existing codebase patterns"
Test Coverage Analyzer: "Check if new code has adequate test coverage"

Phase 5: Synthesize Results

Compile findings from all phases:

Verification Report
===================

Fast Checks (Phase 2):
  [ ] Lint Check: [PASS/FAIL]
  [ ] Type Check: [PASS/FAIL]
  [ ] Build Check: [PASS/FAIL]

Deep Checks (Phase 3):
  [ ] Tests: [X passed, Y failed]
  [ ] Security: [issues found / clean]

Adversarial Review (Phase 4):
  - Logic Issues: [list]
  - Consistency Issues: [list]
  - Coverage Gaps: [list]

Overall Status: [READY TO MERGE / NEEDS WORK]

Recommended Actions:
1. [action item]
2. [action item]

Read the full file on GitHub · 108 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.

2d ago First seen · 108 lines · 9 tokens per session scan A f01278d6cd06

Subscribe to this mod's changes

verify-changes is a command published in the GitHub repository CloudAI-X/opencode-workflow (274 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 707 once invoked, about $0.0000 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-30.

Code review Testing

verify-changes