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 GDvega/super-android-kotlin-firebase-skill --skill firebase-emulator-cigit clone --depth 1 https://github.com/GDvega/super-android-kotlin-firebase-skillWrote 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/gdvega/super-android-kotlin-firebase-skill/firebase-emulator-ci)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/firebase-emulator-ci"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/firebase-emulator-ci/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/gdvega/super-android-kotlin-firebase-skill/firebase-emulator-ci"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/firebase-emulator-ci.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.00030 | $0.00725 |
| Opus 5 | $0.00015 | $0.00362 |
| Sonnet 5 | $0.00006 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
firebase-emulator-ci 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Run Firebase-sensitive tests locally and in CI without touching production projects or open rules.
When to use
- Testing Firebase Security Rules.
- Configuring Firebase Emulator Suite.
- Adding CI for Firestore, Auth, Functions or Storage tests.
- Separating dev, staging and production Firebase environments.
Inputs to inspect
firebase.jsonfirestore.rulesandstorage.rulesfunctions/package files.github/workflows/*package.jsonscriptstest/andandroidTest/
Required workflow
- Identify Firebase products that need emulators.
- Configure emulator ports and project aliases.
- Write rules or functions tests against emulators only.
- Run tests with
emulators:execin CI. - Document environment separation and production safeguards.
Rules
- Do not point emulator tests at production.
- Do not use open rules in production.
- Use
emulators:execfor CI lifecycle when possible. - Keep service accounts out of the repo.
- Fail CI on rules regressions.
Related existing skills
Local skills to invoke
- firebase-core
- firestore
- firebase-cloud-functions
- testing
- security-privacy
External companion skills to use when installed
Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.
- skydoves/android-testing-skills — use for deeper Android or Compose UI testing, semantics, assertions or test workflow guidance.
- firebase/agent-skills — use for deeper Firebase product, Firestore, Security Rules or emulator workflow guidance when installed.
Files commonly touched
firebase.jsonfirestore.rulesstorage.rulesfunctions/package.json.github/workflows/*test/**/*rules*
Commands to validate
firebase emulators:exec --only firestore "npm test"
npm test
./gradlew test
Common mistakes to avoid
- Running tests against real production data.
- Keeping permissive demo rules after setup.
- Starting emulators manually in CI without cleanup.
- Forgetting Storage rules when Firestore is tested.
What ships with it
8 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.
- references/dev-staging-prod-separation.md 188 B
- references/emulator-suite-setup.md 164 B
- references/firestore-rules-testing.md 155 B
- references/github-actions-emulator-ci.md 180 B
- templates/emulator-exec-script-template.md 102 B
- templates/firebase-json-template.md 127 B
- templates/firestore-rules-test-template.md 137 B
- templates/github-actions-firebase-emulator-template.yml 130 B
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.
- 12d ago First seen · 111 lines · 30 tokens per session scan A e7f6d1dd6ce9
firebase-emulator-ci is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 725 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.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
argent-screenshot-diff
Compare saved or live app screenshots with the argent screenshot-diff tool. Use when testing visual regressions, before/after UI comparisons, screenshot diff checks, visible layout, spacing, color, typography, clipping, overflow, text rendering, or image/icon rendering changes.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-qa-flows
Create repeatable QA regression E2E tests as Argent flows from test cases, tickets, or acceptance criteria. Use when the user asks to generate or preserve an automated regression scenario, with deterministic setup, stable targets, executable structural or visual evidence, and two consecutive full passes. For one-off…