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/talayash/agentrium/build-fixgit clone --depth 1 https://github.com/talayash/agentriumWhat 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.00000 | $0.00339 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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 2d 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
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 compilationnpx 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
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.
- 2d ago First seen · 43 lines · 0 tokens per session scan A 5e8537403d19
build-fix is a command published in the GitHub repository talayash/agentrium (39 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.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
validate-gap
Analyze implementation gap between requirements and existing codebase.
spec-impl
Execute spec tasks using TDD methodology.
fix
Auto-detect and fix LSP errors, linting issues, and type errors.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).