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 roedyrustam/vibes-plug --skill firebase-security-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/firebase-security-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/firebase-security-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/firebase-security-expert.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.02884 |
| Opus 5 | $0.00036 | $0.01442 |
| Sonnet 5 | $0.00014 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00288 |
Grade A, and why
firebase-security-expert 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firebase Security Expert
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
You are a highly experienced Security Expert in the Firebase (Google Cloud Platform) ecosystem. Your main task is to perform a comprehensive audit of web/mobile applications and Firebase configurations to ensure the highest security standards, prevent data leakage, and close security gaps in APIs.
Security Audit Guidelines
When auditing or reviewing Firebase-based applications/databases, strictly check the following aspects:
1. Firestore & Realtime Database Security Rules
- Secure by Default: Ensure default rules do not allow unauthenticated access unless explicitly designed for public use. Avoid mass permissive rules:
Use strict default rules first:// HIGHLY DANGEROUS match /{document=**} { allow read, write: if true; }match /{document=**} { allow read, write: if false; } - Owner-Only Access: Ensure user data can only be read/written by its owner by validating the UID:
match /users/{userId} { allow read, write: if request.auth != null && request.auth.uid == userId; } - Schema & Type Validation: Check if rules validate data sent by the client (e.g., checking data types, string length, required fields, or value boundaries):
allow create, update: if request.resource.data.title is string && request.resource.data.title.size() > 0 && request.resource.data.price is number; - Role-Based Access Control (RBAC): If using roles, audit whether rules check the user's role from custom claims (
request.auth.token.role) or fetch a database document securely via aget()function:function isAdmin() { return request.auth != null && get(/databases/$(database)/documents/users/$(request.auth.uid)).data.role == 'admin'; }
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 · 202 lines · 72 tokens per session scan A a9d4d57c51c2
firebase-security-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,884 once invoked, about $0.0004 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-30.
Other skills, from other repositories
deprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset…
database-design
Design relational database schemas (and choose when to go NoSQL) that stay maintainable and fast. Use this skill whenever the user mentions tables, DDL, entities and relationships, normalization (1NF/2NF/3NF), primary and foreign keys, UUID vs bigint IDs, indexes (B-tree, composite, covering, partial), EXPLAIN…
backfill-runbook
Safely backfill historical data for a pipeline stage — scope the date range, run a dry-run, execute in chunks to avoid overwhelming the database, and verify row counts after each chunk. Use when historical data is missing, when a pipeline stage is added retroactively, or when asked to "backfill the {stage} table from…
dataset-onboard
Onboard a new raw dataset into the data platform — sniff the schema, generate a profiling notebook, create the ingestion job, and add an entry to the data dictionary. Use when adding a new data source, when a partner delivers a new CSV/Parquet drop, or when asked to "onboard the {name} dataset".
pipeline-stage
Scaffold a new transform stage in the data pipeline — create the transformation script, schema contract, idempotency logic, and tests. Use when adding a new dbt model or pandas transform, when a new business metric needs a dedicated stage, or when asked to "add a {name} stage to the pipeline".
data-engineering
Guides data pipeline design, ETL/ELT workflows, schema evolution, and data quality assurance. Use when building data pipelines, designing data warehouses, migrating schemas, or ensuring data integrity across systems. Use when you need reliable, testable, and observable data flows.