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 Abdullah4AI/apple-developer-toolkit --skill ui-reviewgit clone --depth 1 https://github.com/Abdullah4AI/apple-developer-toolkitWrote 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/abdullah4ai/apple-developer-toolkit/ui-review)<a href="https://agentmods.dev/skills/abdullah4ai/apple-developer-toolkit/ui-review"><img src="https://agentmods.dev/badge/skills/abdullah4ai/apple-developer-toolkit/ui-review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00571 |
| Opus 5 | $0.00018 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
ui-review 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Build UI Review
After a successful build, capture screenshots and evaluate the visual quality of the generated app. This ensures the UI matches expectations before finalization.
Workflow
Step 1: Capture Screenshots
Call nw_capture_screenshots with the project directory and scheme name. This:
- Boots the iOS simulator
- Builds and installs the app
- Captures the launch screen
- Returns the screenshot path and simulator UDID
Step 2: Evaluate Each Screenshot
Read each screenshot file to view it with your vision capability. For each screen, evaluate against the checklist in references/evaluation-checklist.
Step 3: Collect All Findings
Gather all findings from all screenshots into a single list, ordered by severity:
- Critical — app is broken, blank screen, crash on launch
- High — missing content, broken layout, unreadable text
- Medium — AppTheme violations, spacing issues, alignment problems
- Low — minor polish (shadows, border radius consistency)
Step 4: Fix Sequentially
Fix issues ONE AT A TIME, rebuilding between each fix. This prevents cascading breakage from simultaneous changes to shared components.
Process for each fix:
- Identify the file(s) that need changes
- Make the minimal edit
- Rebuild with
nw_xcode_build - Recapture with
nw_capture_screenshotsto verify the fix - Confirm the fix didn't break other screens
- Move to the next issue
Step 5: Final Verification
After all fixes, do one final nw_capture_screenshots pass. Read the screenshot and confirm all findings are resolved.
Capturing Additional Screens
The simulator stays running after nw_capture_screenshots. To capture other screens:
# Navigate to a different tab/screen (if the app supports deep links)
xcrun simctl openurl <UDID> "myapp://settings"
# Capture the current screen
xcrun simctl io <UDID> screenshot /path/to/project/screenshots/review/settings.png
For apps without deep links, you cannot navigate programmatically — evaluate only the launch screen.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 68 lines · 36 tokens per session scan A 9351a402393a
ui-review is a skill published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 571 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-03.
Other skills, from other repositories
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.