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/validate-buildgit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2Wrote 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/cloudai-x/claude-workflow-v2/validate-build)<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/validate-build"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/validate-build.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00495 |
| Opus 5 | $0.00010 | $0.00247 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
validate-build 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 4d 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
Validate Build
Validate that the project builds successfully. Run BEFORE commits to catch build failures early.
Phase 1: Detect Build System
Identify the project's build system:
# Check for common build configurations
ls package.json Makefile setup.py pyproject.toml go.mod Cargo.toml CMakeLists.txt 2>/dev/null
Phase 2: Run Build Commands
Based on detected system:
Node.js/TypeScript
npm run build 2>&1 || yarn build 2>&1 || pnpm build 2>&1 || bun run build 2>&1
Python
find . -name "*.py" -exec python -m py_compile {} +
# or for packages:
pip install -e . --dry-run
Go
go build ./...
Rust
cargo build
Phase 3: Verify Build Artifacts
Check that expected outputs exist:
dist/orbuild/directory for JS/TS- Compiled binaries for Go/Rust
- No missing dependencies
# Example for Node.js
ls -la dist/ build/ 2>/dev/null
Phase 4: Check for Warnings
Parse build output for:
- Deprecation warnings
- Unused variables/imports
- Performance warnings
- Type coercion warnings
Output Format
## Build Validation: [PASS/FAIL]
### Build Command
[command used]
### Result
- Exit code: [0/non-zero]
- Duration: [time if available]
### Artifacts
- [x] Output directory created
- [x] Expected files present
- [ ] Source maps generated (if applicable)
### Warnings
- [List any build warnings]
### Errors (if failed)
- [Parse and list specific errors]
- [Suggested fixes for each]
Auto-Fix Suggestions
If build fails, suggest:
- Missing dependency installation commands
- Type errors with file:line locations
- Syntax errors with context
- Configuration issues
Usage
This command ships with the project-starter plugin. Invoke with: /project-starter:validate-build
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.
- 4d ago First seen · 107 lines · 20 tokens per session scan A f6fd4a35ecc3
validate-build is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 495 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.
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.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.