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.
npx agentmods add commands/cloudai-x/claude-workflow-v2/verify-changesgit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2What 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.00019 | $0.00874 |
| Opus 5 | $0.00010 | $0.00437 |
| Sonnet 5 | $0.00004 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Changes
Run comprehensive verification of recent code changes using multi-subagent adversarial approach.
Phase 1: Gather Context
Run these commands to understand what changed:
git diff HEAD~1 --stat
git log -3 --oneline
git diff --name-only HEAD~1
Identify affected files and their corresponding test files.
Phase 2: Spawn Verification Subagents (Parallel)
Use the Task tool with run_in_background: true to spawn subagents in parallel.
CRITICAL: Launch ALL subagents in a SINGLE message for true parallelism:
[All Task calls in ONE message]
Task 1: {
description: "Syntax & Type Check",
prompt: "Run language-specific type checker (tsc, mypy, go vet)...",
run_in_background: true
}
Task 2: {
description: "Test Runner",
prompt: "Run tests for affected files first, then integration tests...",
run_in_background: true
}
Task 3: {
description: "Lint & Style Check",
prompt: "Run project linter (eslint, ruff, golangci-lint)...",
run_in_background: true
}
Task 4: {
description: "Security Scan",
prompt: "Grep for hardcoded secrets, check for vulnerabilities...",
run_in_background: true
}
Task 5: {
description: "Build Validator",
prompt: "Run build command, verify artifacts exist...",
run_in_background: true
}
Each subagent returns its result automatically when it completes — there is no separate retrieval call. Read each verifier's report as it returns.
Subagent Details
Subagent 1: Syntax & Type Check
- Run language-specific type checker (tsc, mypy, go vet)
- Report any type errors or warnings
- Exit with list of issues found
Subagent 2: Test Runner
- Run tests for affected files first
- Run related integration tests
- Report failures with file:line context
Subagent 3: Lint & Style Check
- Run project linter (eslint, ruff, golangci-lint)
- Check for formatting issues
- Report violations with severity
Subagent 4: Security Scan
- Grep for hardcoded secrets (passwords, API keys, tokens)
- Check for common vulnerabilities in new code
- Review any new dependencies
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.
- 3d ago First seen · 147 lines · 19 tokens per session scan A e84b2fc15212
verify-changes is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 874 once invoked, about $0.0001 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.
Other commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
build
Run full verification pipeline.
doctor
Run IJFW health check (files, MCP server, hooks, memory, caps, framing).
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.