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 skills add cruisediary/apple-app-review-skills --skill crash-risk-auditgit clone --depth 1 https://github.com/cruisediary/apple-app-review-skillsWrote 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/skills/cruisediary/apple-app-review-skills/crash-risk-audit)<a href="https://agentmods.dev/skills/cruisediary/apple-app-review-skills/crash-risk-audit"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/crash-risk-audit/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/skills/cruisediary/apple-app-review-skills/crash-risk-audit"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/crash-risk-audit.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.00045 | $0.01873 |
| Opus 5.5 | $0.00018 | $0.00749 |
| Sonnet 5.5 | $0.00009 | $0.00375 |
| Haiku 4.5 | $0.00005 | $0.00187 |
Grade A, and why
crash-risk-audit 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Crash Risk Audit
Purpose
Detects force unwraps, force casts, force try, and other crash-prone Swift patterns that can cause unrecoverable crashes during App Store review, violating Guideline 2.1.
Apple Guideline
- Primary: 2.1 — Performance: App Completeness (Crashes)
- Related: 2.1
- Reference:
references/guidelines/2-performance.md
Real-World Rejection Cases
-
Case: Force unwrap crash on nil response — reviewer hit edge case with test data — rejected under 2.1 Source: Apple Developer Forums (multiple threads on crash-related rejections) Root cause: Force unwrap (!) causes EXC_BAD_INSTRUCTION crash at review time on edge-case data — reviewers use test accounts and synthetic data that may produce nil where the developer did not expect it
-
Case: Force cast
as!crash when server returned unexpected type — reviewer triggered during review Source: Developer blogs Root cause: Casting without nil check produces unrecoverable crash — reviewers will encounter this on any data type mismatch between the server and the app's model layer
Trigger
Invoke on any iOS/macOS Swift project before App Store submission to identify high-risk crash patterns.
Inputs
| Name | Type | Default | Description |
|---|---|---|---|
project_root |
path | cwd | iOS/macOS project root |
shared_context |
object | nil | Pre-collected context from appstore-full-audit Phase 1 |
Actions
Phase 1: Context Collection
Skip this phase if shared_context is provided.
Glob**/*.swift— collect all Swift source files.Glob**/*.m— collect Objective-C source files.
Phase 2: Checks
- Force unwrap
Run multiple
Greppatterns in**/*.swiftto catch all force-unwrap variants:[a-zA-Z0-9_]!\.[a-zA-Z]— force unwrap before property/method access (value!.property)[a-zA-Z0-9_]!— force unwrap before space (let x = value!)[a-zA-Z0-9_]!,— force unwrap in argument list (foo(value!, other))[a-zA-Z0-9_]!\)— force unwrap inside parentheses (foo(value!))[a-zA-Z0-9_]!\]— force unwrap before subscript (arr[value!])[a-zA-Z0-9_]!$— force unwrap at end of line (let x = dict["key"]!) Each match that is not in a test target or a SwiftUI#Previewblock → 🔴 CRITICAL per occurrence. Replace withif let,guard let, or??fallback.
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.
- 1mo ago First seen · 147 lines · 45 tokens per session scan A 4d86838a5a7b
crash-risk-audit is a skill published in the GitHub repository cruisediary/apple-app-review-skills (19 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 1,873 once invoked, about $0.0002 per session on Opus 5.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-05.
Other skills, from other repositories
cli-anything-nslogger
CLI harness for NSLogger — parse, filter, export, and monitor NSLogger log files (.rawnsloggerdata / .nsloggerdata).
argent-metro-debugger
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
sentry-app-setup
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.
igf
Use Grapefruit's CLI for platform-specific mobile app inspection and managed captures. Query persisted evidence through the REST API. Use Frida directly for custom scripts and generic runtime primitives.