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 skills add G1Joshi/Agent-Skills --skill firebasegit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/firebase)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/firebase"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/firebase/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/g1joshi/agent-skills/firebase"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/firebase.svg" alt="Reviewed on agentmods" width="80" 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.00405 |
| Opus 5 | $0.00010 | $0.00202 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
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 8d 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.
What it actually says
Firebase (Firestore & Realtime Database)
Firebase provides two NoSQL databases:
- Cloud Firestore: The newer, recommended scalable database.
- Realtime Database: The original low-latency JSON tree sync.
When to Use
- Mobile Apps: Best-in-class integration with Android/iOS/Flutter.
- Realtime Sync: Chat apps, live dashboards.
- Offline Support: Outstanding offline SDK capabilities.
Quick Start (Firestore)
import { getFirestore, collection, addDoc } from "firebase/firestore";
const db = getFirestore(app);
// Add document
await addDoc(collection(db, "users"), {
first: "Ada",
last: "Lovelace",
born: 1815,
});
Core Concepts
Security Rules
Since you access Firebase from the client, you write JSON-like rules to secure it.
service cloud.firestore {
match /databases/{database}/documents {
match /users/{userId} {
allow read, write: if request.auth.uid == userId;
}
}
}
Realtime Updates
Listeners (onSnapshot) keep UI in sync automatically.
Best Practices (2025)
Do:
- Use Firestore Preferentially: It queries and scales better than Realtime DB.
- Use Cloud Functions: For backend logic (sending emails, sanitizing text) triggered by DB events.
- Denormalize: Duplicate data to avoid excessive reads (No joins in Firestore).
Don't:
- Don't use sequential keys: Use auto-generated IDs.
- Don't ignore index limits: Firestore requires composite indexes for sorting/filtering on multiple fields.
References
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.
- 8d ago First seen · 70 lines · 20 tokens per session scan A 758b692ecc0e
firebase is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 405 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
event-driven-architecture-saga-patterns
Designing resilient, eventual-consistency distributed transactions using the Saga Pattern (Choreography and Orchestration). Includes Outbox Pattern, Change Data Capture (CDC), idempotent consumers, compensating transactions, dual-write prevention, and saga recovery mechanisms. Use when implementing distributed…
redis-caching-and-pubsub
Architecting high-performance caching strategies, Cache-Aside/Write-Through/Write-Behind patterns, Redis Pub/Sub, Streams, eviction policies, distributed locking (Redlock), and memory optimization. Use when implementing Redis caching, real-time messaging, rate limiting, or session management.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
architect/data-api-design
A guide to designing data models and application programming interfaces (APIs), which are the rules software uses to exchange data.
backend-development
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.