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/connect-firebasenpx skills add abhinav503/flutter-agentic --skill connect-firebasegit 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/connect-firebase)<a href="https://agentmods.dev/skills/abhinav503/flutter-agentic/connect-firebase"><img src="https://agentmods.dev/badge/skills/abhinav503/flutter-agentic/connect-firebase.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 | $0.00000 | $0.00742 |
| Opus 5 | $0.00000 | $0.00371 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
connect-firebase 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
connect-firebase
Connects one app under apps/{app}/ to a Firebase project. Follow every step in the
guide below. Notes on how this skill splits the work:
1. Pick the app and read its ids
If the app was not passed as an argument, list apps/ and ask which app to connect.
Read and note:
- Android
applicationIdfromapps/{app}/android/app/build.gradle.kts - iOS
PRODUCT_BUNDLE_IDENTIFIERfromapps/{app}/ios/Runner.xcodeproj/project.pbxproj
If either is still com.example.{app}, warn and suggest /change-app-id first.
2. Check both CLIs before asking the user to do anything
Run these yourself:
firebase --version 2>/dev/null || echo "NOT_FOUND"
export PATH="$PATH":"$HOME/.pub-cache/bin" && flutterfire --version 2>/dev/null || echo "NOT_FOUND"
- Firebase missing/broken → give the user the npm install +
~/.zshrcPATH fix from the guide. Wait for them to confirmfirebase --versionworks before continuing. - Firebase not logged in → print
! firebase loginfor the user to run (opens browser). - FlutterFire missing → install it yourself:
dart pub global activate flutterfire_cli
3. Run flutterfire configure yourself (non-interactive)
Ask the user for their Firebase project ID, then run directly — no hand-off needed:
export PATH="$(npm config get prefix)/bin:$HOME/.pub-cache/bin:$PATH"
cd apps/{app} && flutterfire configure \
--project=<firebase-project-id> \
--platforms=android,ios \
--ios-bundle-id=<ios-bundle-id> \
--android-package-name=<android-application-id> \
--yes
After it finishes, verify config files exist using absolute paths (relative ls can miss them):
find /absolute/path/to/apps/{app} -name "firebase_options.dart" \
-o -name "google-services.json" -o -name "GoogleService-Info.plist"
4. Agent does the file edits
pubspec.yaml, main.dart, Gradle — follow the guide. Never add firebase_core to core.
5. Check the Xcode plist registration
flutterfire configure on macOS registers the plist in Xcode automatically. Check before
telling the user to do it manually (doing it again creates a duplicate):
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 · 80 lines · 0 tokens per session scan A c3a6ee918fd2
connect-firebase is a skill published in the GitHub repository abhinav503/flutter-agentic (10 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 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…
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".
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. "스토어 스크린샷 만들어줘", "앱스토어 이미지"…
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.
ui-enhancer-radar
Systematic iOS/SwiftUI UI audit with design intent interview, 14-domain analysis (including Color Audit with adaptive Color Profile, iPad Sheet Sizing caller-side audit, Button Hit Region three-factor interaction audit, and Silent Picker menu-presentation audit), element compaction, cross-view consistency checks…
ui-path-radar
UI path tracer for SwiftUI/UIKit apps. 5-layer audit with 34 issue categories and 19 automated checks: discover entry points, trace flows, detect dead ends and broken promises, evaluate UX impact, verify data wiring. Supports targeted trace, diff against previous audits, and handoff to planning skills. Triggers…