A command that runs the project's Rust or TypeScript checks, finds build errors, and applies the smallest fix it can verify.

Use it when a Rust or TypeScript build fails and you want errors fixed one at a time with a follow-up verification.

It avoids manually locating the first compiler error and making unrelated changes. It checks each fix and stops when the problem needs a larger design change.

How talayash/agentrium configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to talayash/agentrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/talayash/agentrium/master/.claude/commands/build-fix.md

Clone the repo

git clone --depth 1 https://github.com/talayash/agentrium

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/talayash/agentrium/build-fix/github.svg)](https://agentmods.dev/commands/talayash/agentrium/build-fix)

Your own site

<a href="https://agentmods.dev/commands/talayash/agentrium/build-fix"><img src="https://agentmods.dev/badge/commands/talayash/agentrium/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/talayash/agentrium/build-fix"><img src="https://agentmods.dev/badge/commands/talayash/agentrium/build-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 339 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00339
Opus 5.5	$0.00000	$0.00136
Sonnet 5.5	$0.00000	$0.00068
Haiku 4.5	$0.00000	$0.00034

Measured 1mo ago against content hash 5e8537403d19, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/commands/build-fix.md · 43 lines

What it actually says

Build Fix

Automatically detect and fix build errors with minimal changes.

Instructions

Run the build and fix any errors found. Follow this process:

Step 1: Detect Build System

Run these checks in order:

cd src-tauri && cargo check 2>&1 - Rust compilation
npx tsc --noEmit 2>&1 - TypeScript type checking
If a specific build command was mentioned in $ARGUMENTS, run that instead

Step 2: Parse Errors

Identify the FIRST error (fix one at a time)
Note the file path, line number, and error code
Read the relevant code to understand context

Step 3: Apply Minimal Fix

Make the SMALLEST change that resolves the error
Do NOT refactor, restructure, or "improve" surrounding code
Do NOT change unrelated code

Step 4: Verify

Re-run the same build command
If fixed, move to next error
If the fix created MORE errors than it resolved, REVERT and ask for help

Step 5: Guardrails

Stop after 3 failed attempts on the same error - explain what you tried
Stop if fix creates new errors - revert and explain
Never change architecture - if the fix requires restructuring, explain why and ask

Step 6: Report

After all errors are fixed:

## Build Fix Report
- Errors fixed: N
- Files modified: [list]
- Build status: ✅ PASS / ❌ STILL FAILING

Changes

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 · 43 lines · 0 tokens per session scan A 5e8537403d19

Subscribe to this mod's changes

build-fix is a command published in the GitHub repository talayash/agentrium (46 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 339 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-08-30.

Claude Code Productivity builders grid-view profiles vibe-coding

agentrium: Command for Claude Code