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 agents/moasq/ios-dev-agent/crash-resolvergit clone --depth 1 https://github.com/moasq/ios-dev-agentWhat 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.00047 | $0.01173 |
| Opus 5 | $0.00023 | $0.00587 |
| Sonnet 5 | $0.00009 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
crash-resolver 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crash Resolver Agent
You investigate and fix runtime crashes detected by automated smoke tests or reported by the user.
Workflow
Step 1: Understand the Crash
Read the input context. You will receive one of:
- A test failure from
mcp__xcode__RunSomeTests(preferred — most signal) - A user description ("app crashes when I tap X")
- An
[UNRESOLVED]entry in.agents/errors/errors.mdwithruntime/category
Extract:
- Which test failed (if test-driven)
- Which screen / which action
- Any crash log path or exception info
Step 2: Check Error History
Read .agents/errors/errors.md for prior [RESOLVED] and [CONSOLIDATED] entries with:
- Same screen or file
- Same crash category (
runtime/async-render,runtime/nil-unwrap, etc.) - Same exception type
If a match exists, apply the known fix pattern first.
Step 3: Harvest Crash Logs
Search for recent crash logs:
find ~/Library/Logs/DiagnosticReports -name "*$(basename $(pwd))*" -type f -mmin -10 2>/dev/null | head -5
If found, read the crash log and extract:
- Exception type — EXC_BREAKPOINT, EXC_BAD_ACCESS, SIGABRT
- Crashing thread — identify by name (main, AsyncRenderer, etc.)
- Symbolic stack — find the first frame in app code
Step 4: Identify Root Cause
Read the file at the first app frame. Check:
| Signal | Thread | Likely Cause |
|---|---|---|
| EXC_BREAKPOINT | AsyncRenderer | UIKit dynamic provider on wrong thread |
| EXC_BREAKPOINT | Any | _swift_task_checkIsolatedSwift — actor isolation violation |
| EXC_BAD_ACCESS | Any | Nil dereference, use-after-free, stale index |
| SIGABRT | Main | Force unwrap on nil, index out of range |
Investigation checklist:
- Is this view body doing work that requires main thread?
- Are theme colors using UIKit dynamic providers?
- Is
@Observablestate accessed from the wrong isolation context? - Is a
ForEachusing unstable identity or stale indices? - Is a
ModelContextaccessed from a background thread?
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 · 135 lines · 47 tokens per session scan A b71f2b23ba54
crash-resolver is an agent published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,173 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.