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 safe-area-compliancegit 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/safe-area-compliance)<a href="https://agentmods.dev/skills/cruisediary/apple-app-review-skills/safe-area-compliance"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/safe-area-compliance/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/safe-area-compliance"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/safe-area-compliance.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.00039 | $0.01438 |
| Opus 5.5 | $0.00016 | $0.00575 |
| Sonnet 5.5 | $0.00008 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
safe-area-compliance 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Safe Area Compliance
Purpose
Detects unsafe safe-area overrides and hardcoded inset values that hide content behind the Dynamic Island, notch, or home indicator, violating Apple's Human Interface Guidelines for adaptive layout.
Apple Guideline
- Primary: HIG — Adaptivity and Layout (Apple Human Interface Guidelines)
- Related: 2.1
- Reference:
references/hig/adaptive-layout.md
Real-World Rejection Cases
-
Case: Content hidden behind Dynamic Island on iPhone 14 Pro and later Source: Apple Developer Forums Root cause: View used
.edgesIgnoringSafeArea(.all)without compensating insets, pushing interactive controls into the Dynamic Island cutout area. -
Case: Bottom navigation buttons unreachable behind home indicator Source: App Store Connect rejection feedback Root cause: Tab bar and custom buttons were positioned at
y = screenHeight - 49— correct for notchless iPhones but obscured by the home indicator on Face ID devices. -
Case: Developer hardcoded
top: 44inset — broke on devices with different safe areas Source: Apple Developer Forums Root cause: The status-bar height is not a fixed constant; devices with Dynamic Island, notch, or no notch all have different top safe-area values.
Trigger
Invoke on any iOS project that targets iPhone or iPad to verify safe-area insets are respected.
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 Swift source files.Glob**/*.m— collect Objective-C source files.Glob**/*.storyboardand**/*.xib— note Interface Builder files for manual safe-area review.
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 · 130 lines · 39 tokens per session scan A bdb5d1e714fe
safe-area-compliance is a skill published in the GitHub repository cruisediary/apple-app-review-skills (19 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,438 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
apple-design
Complete Apple Human Interface Guidelines (HIG) and Apple Design System standard. Use when designing, building, or auditing UI/UX for iOS, iPadOS, macOS, watchOS, visionOS, or Apple-styled web and mobile applications.
mobile-app
A design template for a single-screen iPhone 15 Pro app mockup, including the phone frame, status bar, app header, main content, and bottom navigation.
mobile-onboarding
A visual template showing three mobile-app onboarding screens side by side: a splash screen, a feature introduction, and sign-in.
add-component
Add a SwiftUI component from ShipSwift. Use when the user says "add component", "add a view", "add X view", "I need a chart", "add animation", or wants a specific UI element.
figma-a11y-annotations
Rules for generating accessibility annotations on iOS/iPadOS mobile designs in Figma. Enforces a bare-minimum annotation discipline, an iOS vocabulary instead of web ARIA terms, and exact grammar for names, control types, page titles, values, hints, headings, groups, and reading order. Never annotates visible text as…
iOS SwiftUI Accessibility
Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 24 WCAG criteria.