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/sangrokjung/claude-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/sangrokjung/claude-forge/build-fix)<a href="https://agentmods.dev/commands/sangrokjung/claude-forge/build-fix"><img src="https://agentmods.dev/badge/commands/sangrokjung/claude-forge/build-fix.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.00012 | $0.00241 |
| Opus 5 | $0.00006 | $0.00120 |
| Sonnet 5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 8d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- ts-build-fix — 86% identical, 9 lines differ
- build-fix — 84% identical, 7 lines differ
- /build-fix — 83% identical, 24 lines differ
What it actually says
참고: 이 스킬은 build-error-resolver 에이전트를 호출하지 않고 인라인 실행됩니다. 에이전트의 memory 학습이 필요하면 Agent 도구로 build-error-resolver를 직접 호출하세요.
Build and Fix
Incrementally fix TypeScript and build errors:
-
Run build: npm run build or pnpm build
-
Parse error output:
- Group by file
- Sort by severity
-
For each error:
- Show error context (5 lines before/after)
- Explain the issue
- Propose fix
- Apply fix
- Re-run build
- Verify error resolved
-
Stop if:
- Fix introduces new errors
- Same error persists after 3 attempts
- User requests pause
-
Show summary:
- Errors fixed
- Errors remaining
- New errors introduced
Fix one error at a time for safety!
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.
- 8d ago First seen · 37 lines · 12 tokens per session scan A 05db4157e3fe
build-fix is a command published in the GitHub repository sangrokjung/claude-forge (825 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 241 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
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
investigate
Systematic root-cause debugging — find the cause before writing any fix.
optimize
Analyze and suggest performance improvements for code, queries, or systems.
perf-profile.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
gates-csk
Gate report — what the tool-level gates actually did, and which rules nothing has tripped.