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/Kasempiternal/axiom-v2Wrote 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/kasempiternal/axiom-v2/fix-build)<a href="https://agentmods.dev/commands/kasempiternal/axiom-v2/fix-build"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/fix-build.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.00019 | $0.00181 |
| Opus 5 | $0.00010 | $0.00090 |
| Sonnet 5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
fix-build 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 6d 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
Fix Build Issues
Launches the build-fixer agent to diagnose and fix Xcode build failures using environment-first diagnostics and resolve SPM dependency conflicts.
What It Does
The agent will:
- Check for zombie xcodebuild processes
- Verify Derived Data size
- Check simulator state
- Analyze SPM dependency conflicts if applicable
- Apply appropriate fixes automatically
- Verify the fixes worked
Prefer Natural Language?
You can also trigger this agent by saying:
- "My build is failing"
- "BUILD FAILED but no error details"
- "Xcode says 'No such module'"
- "SPM won't resolve my dependencies"
- "Getting 'Unable to boot simulator' error"
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.
- 6d ago First seen · 29 lines · 19 tokens per session scan A 02de700d9873
fix-build is a command published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 181 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-31.
Other commands, from other repositories
feature-learn
View and manage patterns learned from feature builds. Shows extracted instincts, confidence scores, and feature completeness history.
feature-plan
Plan a mobile feature with architecture decisions, file breakdown, dependency analysis, and test strategy. Produces a structured plan document reviewed by an architecture agent.
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
add-accessibility
SwiftUI view'lara accessibility identifier ekle. "accessibility ekle", "identifier ekle", "test icin etiketle", "VoiceOver destegi ekle", "erisilebilirlik ekle" gibi isteklerde tetiklenir.
ml-impl
Full implementation loop - plan, write, and review code (Meta-Loop Steps 3.1-3.4).
ml-spec
Full specification loop - plan, write, and review spec (Meta-Loop Steps 2.1-2.4).