What is blueprint-firebase-deploy-production?

A production publishing step that builds the app and deploys that exact build to Firebase Hosting. Hosting is Firebase's service for serving a website on the web.

It is for building the app, attaching a unique build identifier, deploying it to the production project, and checking the served identifier.

It proves that the build verified during development, rather than an untracked variation, is the one running in production.

blueprint-firebase-deploy-production

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 deploy-production

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/receptron/mulmoterminal/deploy-production/github.svg)](https://agentmods.dev/skills/receptron/mulmoterminal/deploy-production)

Your own site

<a href="https://agentmods.dev/skills/receptron/mulmoterminal/deploy-production"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/deploy-production/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/receptron/mulmoterminal/deploy-production"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/deploy-production.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 552 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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00552
Opus 5.5	$0.00007	$0.00221
Sonnet 5.5	$0.00003	$0.00110
Haiku 4.5	$0.00002	$0.00055

Measured 19d ago against content hash 3b364a07e470, 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-deploy-production 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 19d 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/deploy-production/SKILL.md · 38 lines

How it starts

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

Publish to production

This is the deploy-production gate: the user has approved it. Deploy the same source that was verified on dev — do not change anything between the two.

yarn build, then give this build an id and ship it with the site: node -e 'console.log(require("crypto").randomUUID())' > .blueprint/build-id && cp .blueprint/build-id dist/blueprint-build.txt, then firebase deploy --project prod. The check compares the served id with .blueprint/build-id, so it proves THIS build is live. Git is not needed for this.
Tell the user the URL and that the next change should go through dev first.
Write .blueprint/start-here.md, in the spec's language. It is what the person sees the moment the build finishes, so it answers "now what?" in the order they will need it:
- Open it — the production URL (https://<prod-project-id>.web.app) and who can sign in, and how.
- Check that it works — one checkbox per must-have in the spec, each an action and what should happen (- [ ] 申請を 1 件出す → 承認者の一覧に出る), using the app's real screen and button names; one for someone who should be refused (another account, a signed-out visitor) being refused.
- The next change — edit, try it on dev (https://<dev-project-id>.web.app), then publish to production; never straight to production.
- Costs and safety — the budget alert and where it goes; where the security review is (.blueprint/security-review.md).
Keep it short: it is a first page, not the manual.

Done when the check passes: the production site serves the id this deploy wrote to .blueprint/build-id, and .blueprint/start-here.md names the production URL and has the checklist.

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 · 38 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.

19d ago Changed · +13 lines 3b364a07e470
21d ago First seen · 25 lines · 17 tokens per session scan A c64ec2bbbe45

Subscribe to this mod's changes

blueprint-firebase-deploy-production is a skill published in the GitHub repository receptron/mulmoterminal (242 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 552 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.

Claude Code Cloud DevOps and cloud agentic-coding ai-agents codex developer-tools git-worktree

moai-platform-deployment

Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.

modu-ai/moai-adk · 42 tokens

moai-platform-database-cloud

Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.

modu-ai/moai-adk · 51 tokens

stack-baseline

The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…

avelikiy/great_cto · 126 tokens