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 orientation-supportgit 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/orientation-support)<a href="https://agentmods.dev/skills/cruisediary/apple-app-review-skills/orientation-support"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/orientation-support/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/orientation-support"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/orientation-support.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.00043 | $0.01377 |
| Opus 5 | $0.00022 | $0.00688 |
| Sonnet 5 | $0.00009 | $0.00275 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
orientation-support 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Orientation Support
Purpose
Detects missing iPad orientation keys, portrait-only orientation locks, and forced-rotation patterns that cause layout failures when an iPad reviewer rotates their device, violating guideline 2.4.1.
Apple Guideline
- Primary: 2.4.1 — Hardware Compatibility
- Related: 2.1
- Reference:
references/guidelines/2-performance.md
Real-World Rejection Cases
-
Case: iPad app locked to portrait — reviewer rotated device and layout broke Source: App Store Connect rejection feedback Root cause: The app returned only
.portraitfromsupportedInterfaceOrientations, so the iPad reviewer could not use the app in landscape; Apple requires universal apps to support both orientations on iPad. -
Case: Missing
UISupportedInterfaceOrientations~ipad— app treated as iPhone-only on iPad Source: Apple Developer Forums Root cause: Without the iPad-specific plist key, iOS applies the iPhone orientation mask on iPad, which may be portrait-only; the app appeared non-universal and was rejected under 2.4.1.
Trigger
Invoke on any app that declares iPad support (UISupportedInterfaceOrientations~ipad present or UIDeviceFamily includes 2) to verify orientation handling is complete.
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**/Info.plist— locate all Info.plist files.Glob**/*.swift— collect Swift source files for code-level orientation overrides.Glob**/*.m— collect Objective-C source files for the same.
Phase 2: Checks
- iPad orientation key in Info.plist
Readeach Info.plist found in Phase 1. Check thatUISupportedInterfaceOrientations~ipadis present and contains at least one landscape value (UIInterfaceOrientationLandscapeLeftorUIInterfaceOrientationLandscapeRight). Absence of the key → 🟡 MEDIUM. Key present but landscape values absent → 🟡 MEDIUM.
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 · 123 lines · 43 tokens per session scan A 62f1c164015e
orientation-support is a skill published in the GitHub repository cruisediary/apple-app-review-skills (16 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,377 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-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.
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 23 WCAG criteria.
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.
maui-accessibility
Improve MAUI accessibility. USE FOR: semantic labels, hints, headings, screen-reader focus/announcements, AutomationProperties, touch targets, decorative content, TalkBack/VoiceOver/Narrator checks. DO NOT USE FOR: general layout, automation-only tests, performance.