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/CarolaneLFBV/ios-development-agentsWrote 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/carolanelfbv/ios-development-agents/troubleshoot)<a href="https://agentmods.dev/commands/carolanelfbv/ios-development-agents/troubleshoot"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/troubleshoot.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.00017 | $0.00703 |
| Opus 5 | $0.00009 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
troubleshoot 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ios:troubleshoot - iOS Issue Diagnosis
Diagnose and resolve the issue from $ARGUMENTS.
Delegation
Route by --type via the Task tool:
crash/runtime/build/data→ swift-specialistperformance→ performance-specialistui→ swiftui-specialistdeployment→ devops-specialist
Arguments
| Flag | Values | Default | Description |
|---|---|---|---|
--type |
build|crash|performance|runtime|ui|data|deployment | runtime | Issue category |
--debug |
- | - | Interactive debugging mode |
--breakpoints |
- | - | Generate strategic breakpoints |
--trace |
- | - | Enable detailed investigation |
--xcode |
- | - | Include Xcode-specific diagnostics |
--instruments |
- | - | Include Instruments recommendations |
--fix |
- | - | Automatically apply safe fixes |
Issue Categories
| Type | Common Issues |
|---|---|
build |
Compiler errors, dependencies, signing |
crash |
EXC_BAD_ACCESS, SIGABRT, OOM |
performance |
Slow rendering, memory leaks |
runtime |
Data not updating, state issues |
ui |
Layout, Safe Area, Dark mode |
data |
SwiftData sync, persistence |
deployment |
App rejection, entitlements |
Common Fixes
// Force Unwrap Crash
// Before:
let user = users.first!
// After:
guard let user = users.first else { return }
// @Observable Not Updating
// Before:
class UserViewModel { var user: User? }
// After:
@Observable class UserViewModel { var user: User? }
// Memory Leak
// Before:
completion = { self.doSomething() }
// After:
completion = { [weak self] in self?.doSomething() }
LLDB Commands
po view.recursiveDescription() # View hierarchy
thread backtrace all # Thread analysis
watchpoint set variable myVar # Value changes
expr -l Swift -- print(self) # Swift expression
Examples
/ios:troubleshoot "Build failed" --type build --xcode
/ios:troubleshoot "EXC_BAD_ACCESS" --type crash --trace
/ios:troubleshoot "List stutters" --type performance --instruments
/ios:troubleshoot "Data not updating" --type runtime --debug
/ios:troubleshoot "App rejected" --type deployment
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.
- 7d ago First seen · 94 lines · 17 tokens per session scan A c502b567adf9
troubleshoot is a command published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 703 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
flutter-build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
decompile
Decompile an Android APK/XAPK/JAR/AAR and analyze its structure.
safe-decompile
Safely fingerprint and decompile an Android artifact through the sandboxed MCP server.
debug
Debug Purchasely SDK issues — diagnose blank paywalls, frozen UI, purchase failures, and more.
proguard
Command "proguard" from getsentry/cli, covering examples, compute the uuid for a proguard/r8 mapping file, output as json (includes the file path) and important notes.
xcode-build-fix
Incrementally fix Xcode build and Swift compiler errors. Parse errors, explain issues, apply fixes, verify resolution.