push-notifications

A guide for adding push notifications—messages sent to a phone by an app—to Flutter apps using Firebase Cloud Messaging (FCM). It covers iOS and Android delivery, app states, and notification links.

In plain words
What is it for?
Use it to configure FCM, set up Apple's notification service, open specific app screens from notifications, subscribe users to topics, or show local notifications.
Why use it?
It helps handle the platform setup and the different ways notifications behave when an app is open, closed, or running in the background.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/launch52-ai/flutter-template/push-notifications
Any agent
npx skills add launch52-ai/flutter-template --skill push-notifications
Clone the repo
git clone --depth 1 https://github.com/launch52-ai/flutter-template

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,095 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.01095
Opus 5 $0.00022 $0.00548
Sonnet 5 $0.00009 $0.00219
Haiku 4.5 $0.00004 $0.00110

Measured 2d ago against content hash 0a8c710f6a3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

push-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.

.claude/skills/push-notifications/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Push Notifications - Firebase Cloud Messaging

Push notifications with FCM for iOS and Android. Handles foreground, background, and terminated app states.

When to Use This Skill

  • Adding push notifications to a Flutter app
  • Configuring Firebase Cloud Messaging
  • Setting up APNs for iOS
  • Implementing deep linking from notifications
  • User asks "add push notifications", "FCM setup", or "notification handling"

Questions to Ask

  1. Firebase project: Is Firebase already configured, or need to set up from scratch?
  2. Notification types: Marketing notifications only, or also transactional (in-app events)?
  3. Deep linking: Should notifications open specific screens?
  4. Topics: Need topic-based subscriptions (e.g., "news", "promotions")?
  5. Local notifications: Need scheduled/local notifications (non-push)?

Reference Files

reference/
├── models/           # Notification payload (Freezed)
├── services/         # FCM initialization, handlers
├── repositories/     # Domain interface + impl + mock
├── providers/        # Riverpod notifiers + state
└── failures/         # Sealed Failure types

templates/ios/        # Info.plist additions
templates/android/    # AndroidManifest, build.gradle

See: implementation-guide.md for complete setup.

Workflow

Phase 1: Firebase Setup

  1. Create Firebase project (if needed)
  2. Add iOS app with APNs key (see firebase-setup-guide.md)
  3. Add Android app with SHA-1 fingerprints
  4. Download config files (GoogleService-Info.plist, google-services.json)

Phase 2: Platform Config

  1. iOS: Add Push Notification capability, Background Modes
  2. Android: Add FCM dependencies and manifest entries
  3. Add config files to project

Phase 3: Implementation

  1. Copy reference files to project
  2. Initialize FCM in main.dart
  3. Implement token registration with backend
  4. Add notification handlers (foreground/background/terminated)
  5. Configure deep linking (optional)

Core API

Read the full file on GitHub · 140 lines

Changes

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.

  1. 2d ago First seen · 140 lines · 44 tokens per session scan A 0a8c710f6a3a

Subscribe to this mod's changes

push-notifications is a skill published in the GitHub repository launch52-ai/flutter-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 1,095 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.

Related

Other skills, from other repositories