blueprint-firebase-projects

blueprint-firebase-projects is a skill for Claude Code, Codex from receptron/mulmoterminal. It costs 24 tokens per session (516 once invoked), scanned A, original, MIT.

A Firebase project setup for separate development and production projects. It creates or selects the projects, configures Firestore and web apps, and places aliases in the local Firebase configuration.

In plain words
What is it for?
It is for creating or choosing the two projects, setting their Firestore region, registering web apps, and preparing Firebase aliases for each environment.
Why use it?
Separate projects reduce the chance that testing changes real user data or production settings; the billing-plan change requires the user to confirm it in the console.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for creating or choosing the two projects, setting their Firestore region, registering web apps, and preparing Firebase aliases for each environment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/receptron/mulmoterminal/projects
Install

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.

Any agent
npx skills add receptron/mulmoterminal --skill projects
Clone the repo
git clone --depth 1 https://github.com/receptron/mulmoterminal

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for blueprint-firebase-projects

README.md
[![agentmods](https://agentmods.dev/badge/skills/receptron/mulmoterminal/projects/github.svg)](https://agentmods.dev/skills/receptron/mulmoterminal/projects)
Your own site
<a href="https://agentmods.dev/skills/receptron/mulmoterminal/projects"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/projects/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.

agentmods 80×15 button for blueprint-firebase-projects

Your own site · 80×15
<a href="https://agentmods.dev/skills/receptron/mulmoterminal/projects"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/projects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 516 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00516
Opus 5.5 $0.00010 $0.00206
Sonnet 5.5 $0.00005 $0.00103
Haiku 4.5 $0.00002 $0.00052

Measured 25d ago against content hash c72c25224cee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blueprint-firebase-projects 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 25d 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.

blueprints/firebase/skills/projects/SKILL.md · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev and production projects

Read .blueprint/spec.md for existingProject, existingProjectId and region.

  1. Two projects: dev and production. If the user named an existing one, use it for production and create only dev. Project ids are global — propose <app>-dev / <app>-prod and ask if they are taken.
  2. firebase projects:create <id> for each new one, then write .firebaserc with aliases dev and prod (firebase use --add).
  3. Billing is the gate for this step and the executor has already had it approved. Linking a billing account (Blaze) is done by the user in the console: give them the exact URL https://console.firebase.google.com/project/<id>/usage/details and wait for them to confirm. Do not try to link billing from the CLI on their behalf.
  4. Create Firestore in region for BOTH projects. The region cannot be changed later — read it back from the spec, never assume a default.
  5. Each project needs a registered web app — Hosting serves its config at /__/firebase/init.json, which the app reads. firebase apps:list WEB --project <id>; if none, firebase apps:create WEB <app name> --project <id>.
  6. Google sign-in must be switched on in each project. sh <base pack>/checks/google-signin.sh dev (and prod) reads it; for each that fails, give the user the URL it printed and wait — enabling it creates an OAuth client, which only the console can do.

Done when the check passes: .firebaserc has distinct dev and prod projects, both exist, both have billing enabled and both have a Firestore database.

Always

  • Read .blueprint/spec.md first. It is the agreed specification; do not widen it.
  • When you need a decision, ask it through the blueprint question tool and stop. Do not guess.
  • Never enable billing, deploy to production, delete data or handle a credential unless this step's gates say the user approved exactly that.
  • Say you are done by stopping; the executor runs the check. Do not claim success yourself.

Read the full file on GitHub · 36 lines

Changes

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.

  1. 25d ago First seen · 36 lines · 24 tokens per session scan A c72c25224cee

Subscribe to this mod's changes

blueprint-firebase-projects is a skill published in the GitHub repository receptron/mulmoterminal (244 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 516 once invoked, about $0.0001 per session on Opus 5.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-28.

Related

Other skills, from other repositories