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.
git clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/build-fix)<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/build-fix"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/build-fix/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.
<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/build-fix"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/build-fix.svg" alt="Reviewed on agentmods" width="80" 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.01756 |
| Opus 5.5 | $0.00000 | $0.00702 |
| Sonnet 5.5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
build-fix 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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
快速修复构建错误和类型问题。使用最小改动原则，专注于解决编译和类型检查失败。
语法
/build-fix [options]
参数
| 参数 | 类型 | 必需 | 说明 |
|---|---|---|---|
--error |
string | 否 | 具体的错误信息 |
--file |
string | 否 | 错误所在的文件路径 |
--strict |
flag | 否 | 严格模式，不允许类型断言等妥协 |
--check-only |
flag | 否 | 仅检查不修复 |
使用示例
自动检测并修复
/build-fix
运行构建命令，自动检测并修复所有错误。
修复特定错误
/build-fix --error "Property 'name' does not exist on type 'User'"
针对特定错误进行修复。
修复特定文件
/build-fix --file src/auth/login.ts
仅检查并修复指定文件的错误。
严格模式
/build-fix --strict
不使用 any、类型断言等妥协方案。
执行流程
┌─────────────────────────────────────────────────────────────────┐
│ /build-fix 执行流程 │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌───────────────────────────────────────────────────┐ │
│ │ 检测阶段 │ │
│ │ • 运行构建命令 (npm run build / tsc) │ │
│ │ • 收集所有错误 │ │
│ │ • 按文件和行号分组 │ │
│ └───────────────────────┬───────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌───────────────────────────────────────────────────┐ │
│ │ 分析阶段 │ │
│ │ • 识别错误类型 │ │
│ │ • 确定根因 │ │
│ │ • 计划最小修复 │ │
│ └───────────────────────┬───────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌───────────────────────────────────────────────────┐ │
│ │ 修复阶段 │ │
│ │ 对每个错误: │ │
│ │ • 应用最小修复 │ │
│ │ • 验证修复 │ │
│ │ • 检查是否引入新错误 │ │
│ └───────────────────────┬───────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌───────────────────────────────────────────────────┐ │
│ │ 验证阶段 │ │
│ │ • 重新运行构建 │ │
│ │ • 确认所有错误已修复 │ │
│ │ • 运行测试确认无回归 │ │
│ └───────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
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.
- 1mo ago First seen · 233 lines · 0 tokens per session scan A 1c325654af4c
build-fix is a command published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,756 tokens. 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-09-05.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.