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 skills/moasq/ios-dev-agent/notificationsnpx skills add moasq/ios-dev-agent --skill notificationsgit 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.00024 | $0.00572 |
| Opus 5 | $0.00012 | $0.00286 |
| Sonnet 5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
notifications 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Notifications
Use this guide when implementing or modifying notification features.
Framework
UserNotifications — UNUserNotificationCenter.current()
Permission States (CRITICAL — handle ALL four)
- Not Determined — Call
.requestAuthorization(options: [.alert, .badge, .sound]). System shows dialog. - Authorized — Schedule notifications normally.
- Denied — App CANNOT re-request. Must redirect user to System Settings.
- Provisional — Quiet notifications. Treat as authorized.
Permission Is System-Controlled
- Once denied, the app has NO way to re-request — only the user can re-enable in System Settings.
- To open Settings:
UIApplication.shared.open(URL(string: UIApplication.openSettingsURLString)!)
UI Rules for Notification Status
.notDetermined— Show "Enable Notifications" button that callsrequestAuthorization. After dialog, re-check and update UI..authorized/.provisional— Show enabled state (bell icon). Read-only — user disables in Settings..denied— Show "bell.slash" icon + "Open Settings" button. Show helper text explaining system control.- NEVER use a writable Toggle for notification permission — the app cannot grant/revoke it. Use buttons with state-specific actions.
Re-Check on Foreground (CRITICAL)
Any view displaying notification status MUST re-check when app returns to foreground:
.onReceive(NotificationCenter.default.publisher(for: UIApplication.willEnterForegroundNotification)) { _ in
Task {
let settings = await UNUserNotificationCenter.current().notificationSettings()
isEnabled = (settings.authorizationStatus == .authorized || settings.authorizationStatus == .provisional)
}
}
Scheduling
let content = UNMutableNotificationContent()
content.title = "Reminder"
content.body = "Time to check in"
content.sound = .default
// Time-based
let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 3600, repeats: false)
// Calendar-based (daily at specific time)
var dateComponents = DateComponents()
dateComponents.hour = 20
dateComponents.minute = 0
let trigger = UNCalendarNotificationTrigger(dateMatching: dateComponents, repeats: true)
let request = UNNotificationRequest(identifier: "reminder", content: content, trigger: trigger)
try await UNUserNotificationCenter.current().add(request)
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 · 63 lines · 24 tokens per session scan A 6b6268bb4dec
notifications is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 572 once invoked, about $0.0001 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 skills, from other repositories
edge-to-edge
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
flutter-fix-layout-issues
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…