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/ahmed3elshaer/everything-claude-code-mobileWrote 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/ahmed3elshaer/everything-claude-code-mobile/feature-build-fix)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-build-fix"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-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.00026 | $0.00483 |
| Opus 5 | $0.00013 | $0.00242 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
feature-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 4d 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
Feature Build Fix Command
Phase 4 of the feature build pipeline. Iteratively compiles and fixes until the feature builds and all tests pass.
Usage
/feature-build-fix auth
/feature-build-fix offline-cache
/feature-build-fix push-notifications
Workflow Loop (Max 5 Iterations)
┌─→ 1. Compile
│ ├─ Android: ./gradlew build
│ └─ iOS: xcodebuild build
│
│ 2. Compile failed?
│ ├─ Android → android-build-resolver fixes errors
│ └─ iOS → xcode-build-resolver fixes errors
│ └─ Go to step 1
│
│ 3. Compile passed → Run tests
│ ├─ Android: ./gradlew test connectedAndroidTest
│ └─ iOS: xcodebuild test
│
│ 4. Tests failed?
│ └─ mobile-tdd-guide analyzes and fixes failures
│ └─ Go to step 1
│
└── 5. All pass → Phase complete ✓
Iteration Tracking
Each iteration is logged in .omc/state/feature-{name}.json:
build-fix:
iteration: 3
max: 5
history:
- { round: 1, compile: fail, errors: 12 }
- { round: 2, compile: pass, tests: fail, failures: 4 }
- { round: 3, compile: pass, tests: pass }
status: completed
Escalation
If max iterations (5) reached without full success:
- Reports remaining compile errors and test failures to user
- Lists blocked items with suggested manual fixes
- State marked as
blockedfor/feature-statusvisibility
Invokes
android-build-resolveragent (Android compile errors)xcode-build-resolveragent (iOS compile errors)mobile-tdd-guideagent (test failure analysis and fixes)
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.
- 4d ago First seen · 67 lines · 26 tokens per session scan A 781fe3a3ecf7
feature-build-fix is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (66 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 483 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-09-03.
Other commands, from other repositories
test-simulator
Launch simulator testing agent for test scenarios and visual verification.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.