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/abhinav503/flutter-agentic/add-notification-featurenpx skills add abhinav503/flutter-agentic --skill add-notification-featuregit clone --depth 1 https://github.com/abhinav503/flutter-agenticWrote 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/abhinav503/flutter-agentic/add-notification-feature)<a href="https://agentmods.dev/skills/abhinav503/flutter-agentic/add-notification-feature"><img src="https://agentmods.dev/badge/skills/abhinav503/flutter-agentic/add-notification-feature.svg" alt="Measured on agentmods" 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.00000 | $0.01563 |
| Opus 5 | $0.00000 | $0.00781 |
| Sonnet 5 | $0.00000 | $0.00313 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
add-notification-feature 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-notification-feature
Adds Firebase Cloud Messaging (FCM) push notifications to one app under
apps/{app}/: device token, foreground/background/terminated handling, topic
subscriptions, tap-to-open-a-page routing, and image (rich) notifications.
FCM only — no CleverTap.
The guide is split into platform tracks — present the steps separated by iOS and Android so the user can follow only the platform(s) they ship:
- Part A — Shared Flutter code (deps + Dart): identical for both platforms; always do it.
- Part B — iOS track: Apple/Firebase credential + Xcode capabilities.
- Part C — Android track: manifest permission + channel.
- Part D — Test: separate iOS and Android instructions.
Follow every step in the guide below. Notes on how this skill splits the work:
1. Pick the app, platform(s), and confirm Firebase is connected
If the app was not passed as an argument, list apps/ and ask which one. Also ask
which platform(s) it targets — that decides whether you do Part B, Part C, or
both.
This skill builds on /connect-firebase — it does not run the FlutterFire
CLI itself. Verify the app is already connected:
ls apps/{app}/lib/firebase_options.dart
grep -n "firebase_core" apps/{app}/pubspec.yaml
grep -n "Firebase.initializeApp" apps/{app}/lib/main.dart
If any is missing → stop, tell the user to run /connect-firebase first, then
return here.
2. Part A — shared Flutter code (agent, both platforms)
Add firebase_messaging + flutter_local_notifications to this app's
pubspec.yaml (never core), then create under
apps/{app}/lib/services/notification/ the payload, navigator key, local
notification service, router, and FirebaseMessagingService (static singleton — not
in GetIt), plus notification_type.dart enums. Register the background handler in
main.dart; call FirebaseMessagingService.instance.init() from the home
screen's addPostFrameCallback. This part is platform-agnostic.
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.
- 6d ago First seen · 126 lines · 0 tokens per session scan A 93b890a40320
add-notification-feature is a skill published in the GitHub repository abhinav503/flutter-agentic (10 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,563 tokens. 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
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…
testing-flutter
Testing Flutter 3.44 / BLoC v9 / Riverpod 3 - Stratégie Complète. Use when writing tests, reviewing test coverage, or setting up testing.
kotlin-android
Use when building or fixing a native Android app in Kotlin and Jetpack Compose on the UDF layered architecture — ViewModel/StateFlow, Hilt, Room, Retrofit, coroutines, type-safe Navigation, and the Gradle/AGP surface. NOT shared Android and iOS UI from one Kotlin codebase (that is compose-multiplatform).
store-screenshots
앱스토어·플레이스토어 등록용 마케팅 스크린샷 자동 생성. 원본 앱 스크린샷에 기기 프레임(iPhone, iPad, Galaxy, Fold, Flip)을 씌우고 배경 그라데이션과 홍보 문구를 얹어 스토어 규격 PNG로 출력한다. Turns raw app screenshots into store-ready App Store & Google Play marketing images — device frames, branded backgrounds, marketing copy, exact store sizes. "스토어 스크린샷 만들어줘", "앱스토어 이미지"…
workflow-audit
Systematic UI workflow auditing for SwiftUI applications. Discovers entry points, traces user flows, detects dead ends and broken promises, audits data wiring, evaluates from user perspective. Triggers: "workflow audit", "audit flows", "find dead ends", "check navigation".
app-store-deployment
Publishes mobile applications to iOS App Store and Google Play with code signing, versioning, and CI/CD automation. Use when preparing app releases, configuring signing certificates, or setting up automated deployment pipelines.