Borrowing it
Nothing to install: this file belongs to tutur3u/platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tutur3u/platform/main/.agents/skills/firebase-remote-config-basics/SKILL.mdgit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/firebase-remote-config-basics)<a href="https://agentmods.dev/skills/tutur3u/platform/firebase-remote-config-basics"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/firebase-remote-config-basics.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.00020 | $0.00976 |
| Opus 5 | $0.00010 | $0.00488 |
| Sonnet 5 | $0.00004 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
firebase-remote-config-basics 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.
This is a copy
94% identical to firebase-remote-config-basics — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Config
This skill provides a complete guide for getting started with Remote Config on Android or iOS. Remote Config allows you to change the behavior and appearance of your app without publishing an app update by maintaining a cloud-based configuration template.
Prerequisites
Provisioning Remote Config requires both a Firebase project and a Firebase app,
either Android or iOS. To manage the Remote Config template and conditions via
the command line, use the Firebase CLI. See the firebase-basics skill for
references on project initialization.
Troubleshooting Execution
Handling npx 403 Forbidden Errors
If npx -y firebase-tools@latest fails due to registry permissions (403 error):
- Inform the user: "I am unable to fetch the latest Firebase tools via npx due to a registry error."
- Fallback: Attempt to use the local
firebasecommand directly if the user confirms it is installed globally (npm install -g firebase-tools).
Handling Project Context Issues
If a command fails because "no active project is selected":
- Check login: Run
npx -y firebase-tools@latest login:list. - Prompt for ID: If logged in but no project is active, ask the user: "Please provide your Firebase Project ID to proceed."
- Use Flag: Append
--project <PROJECT_ID>to every subsequent command.
SDK Setup
To learn how to set up Remote Config in your application code, choose your platform:
- Android: android_setup.md
- iOS: ios_setup.md
Best Practices and Template Management
Follow these guidelines and use the associated CLI tools to ensure efficient and safe use of Remote Config.
Fetching Strategies
To optimize app performance and user experience, follow these recommended patterns (see Loading Strategies):
- Load new values for next startup: The most effective pattern is to activate previously fetched values immediately on startup and fetch new values in the background to be used next time. This minimizes user wait time.
- Real-time Updates: Use the SDK's real-time listener to update the app instantly without a refresh when server-side configuration changes.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -7 lines · -25 tokens per session 678dd5bb907d
- 8d ago First seen · 125 lines · 45 tokens per session scan A 87b472695dcd
firebase-remote-config-basics is a skill published in the GitHub repository tutur3u/platform (53 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 976 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to firebase-remote-config-basics, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
frontend-engineer
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults" !cat .forgewright/codebase-context.md…
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
subscriptions
Set up real-time event streams with async generator subscriptions using .subscription(async function() { yield }). SSE via httpSubscriptionLink is recommended over WebSocket. Use tracked(id, data) from @trpc/server for reconnection recovery with lastEventId. WebSocket via wsLink and createWSClient from @trpc/client…
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.