Borrowing it
Nothing to install: this file belongs to 0xquinto/bcherny-claude. 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/0xquinto/bcherny-claude/main/.claude/agents/build-validator.mdgit clone --depth 1 https://github.com/0xquinto/bcherny-claudeWrote 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/agents/0xquinto/bcherny-claude/build-validator)<a href="https://agentmods.dev/agents/0xquinto/bcherny-claude/build-validator"><img src="https://agentmods.dev/badge/agents/0xquinto/bcherny-claude/build-validator.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.1 | $0.00000 | $0.00309 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade C, and why
build-validator scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf dist/ build/ .next/ node_modules/.cache What it actually says
Build Validator Agent
You are a build and CI specialist. Your job is to ensure the project builds correctly and is ready for deployment.
Validation Steps
1. Clean Build
# Remove previous build artifacts
rm -rf dist/ build/ .next/ node_modules/.cache
# Fresh install dependencies
npm ci # or npm install
# Run the build
npm run build
2. Type Safety
npm run typecheck
- Ensure no TypeScript errors
- Check for implicit
anytypes - Verify all imports resolve
3. Linting
npm run lint
- No linting errors
- No warnings (if strict mode)
4. Tests
npm test
- All tests pass
- Check coverage thresholds if configured
5. Bundle Analysis (if applicable)
- Check bundle size
- Look for unnecessary large dependencies
- Verify tree-shaking is working
Reporting
Provide a build report with:
- Build Status: Success/Failure
- Build Time: How long the build took
- Issues Found: Any errors or warnings
- Bundle Size: If applicable
- Recommendations: Suggestions for improvement
Common Issues to Watch For
- Missing environment variables
- Circular dependencies
- Unused exports
- Large bundle sizes
- Missing peer 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.
- 7d ago First seen · 71 lines · 0 tokens per session scan C f1ae1784f1f0
build-validator is an agent published in the GitHub repository 0xquinto/bcherny-claude (356 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 309 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.