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/nylo-core/claude-code/nylo-notificationsnpx skills add nylo-core/claude-code --skill nylo-notificationsgit clone --depth 1 https://github.com/nylo-core/claude-codeWhat 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.00039 | $0.03075 |
| Opus 5 | $0.00019 | $0.01537 |
| Sonnet 5 | $0.00008 | $0.00615 |
| Haiku 4.5 | $0.00004 | $0.00308 |
Grade A, and why
nylo-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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nylo Local Notifications
Overview
Nylo v7 provides a LocalNotification class for sending immediate or scheduled local notifications on iOS and Android. It wraps platform-specific notification APIs behind a fluent builder pattern, with static convenience methods for common operations. Local notifications are not supported on web and will throw a NotificationException if attempted.
When to Use
- Sending immediate local notifications to the user
- Scheduling notifications for a future date/time
- Configuring Android notification channels (importance, vibration, LEDs, sounds)
- Configuring iOS notification presentation (banners, alerts, badges, interruption level)
- Attaching media to iOS notifications
- Handling notification permissions
- Cancelling or clearing notifications
- Managing app badge counts
- When NOT to use: For push notifications from a remote server, use a dedicated push notification service (e.g., Firebase Cloud Messaging). This skill covers local-only notifications.
Quick Reference
| Action | Code |
|---|---|
| Send immediately | await LocalNotification(title: "Hi", body: "World").send() |
| Send with helper | await localNotification("Hi", "World").send() |
| Send via static method | await LocalNotification.sendNotification(title: "Hi", body: "World") |
| Schedule for later | .send(at: DateTime.now().add(Duration(hours: 1))) |
| Add payload | .addPayload("order_id:456") |
| Set notification ID | .addId(42) |
| Add subtitle | .addSubtitle("From support") |
| Set badge number | .addBadgeNumber(3) |
| Custom sound | .addSound("alert.wav") |
| iOS attachment | .addAttachment("https://example.com/img.jpg", "img.jpg") |
| Android config | .setAndroidConfig(AndroidNotificationConfig(...)) |
| iOS config | .setIOSConfig(IOSNotificationConfig(...)) |
| Cancel by ID | await LocalNotification.cancelNotification(42) |
| Cancel all | await LocalNotification.cancelAllNotifications() |
| Request permissions | await LocalNotification.requestPermissions() |
| Clear badge count | await LocalNotification.clearBadgeCount() |
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 · 393 lines · 39 tokens per session scan A 339e794bc628
nylo-notifications is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 3,075 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-08-31.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
dart-3-updates
Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.