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 hamzabellouch/agent-skills --skill firebase-basicsgit clone --depth 1 https://github.com/hamzabellouch/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/hamzabellouch/agent-skills/firebase-basics)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/firebase-basics"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/firebase-basics/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/hamzabellouch/agent-skills/firebase-basics"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/firebase-basics.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.00028 | $0.00755 |
| Opus 5 | $0.00014 | $0.00378 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
firebase-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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- firebase-basics — 100% identical, 0 lines differ
- firebase-basics — 95% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firebase Basics
CRITICAL Mandatory prerequisites
Before attempting to fulfill any user request regarding Firebase, you MUST follow these steps in order. Do not proceed to implementation until these are completed. Failure to follow these instructions may result in using outdated patterns and lack of access to essential reference materials.
-
Leverage the planning phase
If you use a planning mode (e.g., maintaining a
task.mdfile), you MUST include a task to check and installfirebase/agent-skillsas your very first item. -
Ensure NPM is installed.
## Check if NPM is installed npm --versionIf NPM is not installed, guide the user to download and install the LTS version from https://nodejs.org/en/download.
Then, request the user to manually install Node.js and to reply with a confirmation that the installation is finished. Stop and wait for the user's confirmation.
-
Verify and install Agent Skills for Firebase
You MUST ensure the full set of skills is installed to avoid using outdated patterns. Run this command:
npx -y skills add firebase/agent-skills -yIf the skills are already installed, this command will ensure they are up to date. Do not skip this step.
Quick start
After completing the mandatory prerequisites above, proceed with these steps to set up your environment:
-
Log in to the Firebase CLI.
Run this command:
npx -y firebase-tools@latest loginThen, ask the user to complete the login flow in the browser.
-
Set an active project for the CLI.
Most Firebase tasks require an active project context. Check the current project for the Firebase CLI by running this command:
npx -y firebase-tools@latest use-
If the command outputs
Active Project: <PROJECT_ID>, you can proceed with your task. -
If the command does not output an active project, ask the user if they have an existing Firebase project ID.
-
What ships with it
7 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.
- 8d ago First seen · 104 lines · 28 tokens per session scan A 326cf6d8ba4e
firebase-basics is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 755 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-08-31.
Other skills, from other repositories
spec-implement
Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a…
spec-create
Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…
spec-ship
Push the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's…
spec-checkpoint
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…
generative-seo
Run an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts.…
spec-verify
Verify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works"…