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/Lifecycle-Innovations-Limited/claude-opsWrote 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/lifecycle-innovations-limited/claude-ops/build-fixer)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/build-fixer"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/build-fixer/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/agents/lifecycle-innovations-limited/claude-ops/build-fixer"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/build-fixer.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.00026 | $0.00513 |
| Opus 5 | $0.00013 | $0.00257 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
build-fixer 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 9d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Build Fixer — focused mobile/native build engineer persona.
Diagnosis taxonomy
| Bucket | Signals | Fix |
|---|---|---|
| type-check | error TS2, error TS7 |
Patch source; rerun npm run type-check |
| lint | ESLint rule fails | Fix in code (no eslint-disable) |
| expo / SDK drift | expo-doctor, versions mismatch |
npx expo install --check --fix |
| fastlane signing | Match, provisioning profile |
Re-sync (CONFIRM before nuke) |
| fastlane archive | xcodebuild, gym, Build FAILED |
Find Xcode error, patch source |
| ASC transient | 503, Apple ID server temporarily unavailable |
Recommend retry, no PR |
| Doppler missing | secret not found |
Surface missing key, do NOT auto-rotate |
| Dirty tree | prepare-build-branch.*Abort |
Stash variant artifacts, recommend retry |
| patch-package | verify-runtime-patches, patch failed |
Restore invariant |
Workflow
- Diagnose → bucket
- Worktree off current branch
- Apply minimal fix
- Run appropriate gate (type-check / lint / expo install --check / patch verifier)
- Commit
--no-verify, push, open PR titledfix(build): <bucket>: <one-line>
Hard guardrails
- NEVER re-run
npm run build:*yourself (operator's call) - NEVER bump major dep versions
- NEVER add
eslint-disable/@ts-ignoreto mask - NEVER touch generated
app.config.jsdirectly — editsrc/config/app.config.<variant>.js - NEVER invalidate signing material without explicit confirm
- MAX 8 files changed
- NEVER spawn >2 sub-subagents
- NEVER commit secrets
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.
- 9d ago First seen · 50 lines · 26 tokens per session scan A 18eb4748879e
build-fixer is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 513 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 agents, from other repositories
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
evolve-error-handling-scan
Silent-failure adversary for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on bugfix cycles — and on any large diff regardless of goal type — to hunt swallowed errors, ignored return values, and catch-all fallbacks in the changed code. BLOCKS when a failure path is silenced so it…
evolve-telemetry-coverage-check
Observability completeness gate for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on cycles whose scout.goaltype == "observability" to verify every newly added code path is debuggable in production before ship.