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 receptron/mulmoterminal --skill import-firebasegit clone --depth 1 https://github.com/receptron/mulmoterminalWrote 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/receptron/mulmoterminal/import-firebase)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/import-firebase"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/import-firebase/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/receptron/mulmoterminal/import-firebase"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/import-firebase.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.00033 | $0.00623 |
| Opus 5.5 | $0.00013 | $0.00249 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
blueprint-from-collection-import 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Move the records in (emulators)
Read .blueprint/source/source.json first. If records is false, only the shape was copied: there is nothing to
move. Add a yarn import-source script that says so and exits 0, and stop.
Otherwise the records are in .blueprint/source/collections/<slug>/records.jsonl (one JSON object per line), and the
files they point at are under .blueprint/source/files/, at the path the record names.
- Add
yarn import-source --target emulator|prod, using the Admin SDK (firebase-admin, a dev dependency — it never ships to the client).emulator: the project iddemo-blueprint; the emulator hosts come from the environmentfirebase emulators:execsets, so no key is needed.prod: the production project from.firebaserc, with the person's Application Default Credentials. Never read a service account key file. - Names follow the spec and the pack's
spec/conversion.md(Firestore): the collection is the slug; the document id is the primary key's value; a stored field keeps its key. A boolean stays a boolean, a number a number, a date its ISO text, arefthe referenced id as text. - A record's
image/filevalue is a path: upload.blueprint/source/files/<path>to the default bucket at the same path, and keep the path in the field. If any file is uploaded, add the Storage emulator andstorage.rules(deny by default; open only what the spec says), and write the bucket's name to.blueprint/storage-bucket. - Running it twice leaves the same documents (
setby id, neveradd). - A record that does not fit is not dropped silently: the script stops and names the collection, the record's id and the field.
- The rules are not loosened for the import: the Admin SDK does not go through them.
Done when the check passes: inside the emulators, run twice, every collection has as many documents as it had records,
every stored field reads back equal, and every pointed-at file is in the bucket named in .blueprint/storage-bucket.
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.
- 25d ago First seen · 39 lines · 33 tokens per session scan A 46e13d0a00ac
blueprint-from-collection-import is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 623 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-30.
Other skills, from other repositories
moai-domain-database
Database specialist covering PostgreSQL, MongoDB, Redis, Oracle, and cloud database platforms (Neon, Supabase, Firestore). Use for schema design, query optimization, indexing strategies, data modeling, or cloud database selection. Cloud vendor guide absorbed from moai-platform-database-cloud.
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.
optimize
Analyze and suggest performance improvements for code, queries, or systems.
migration-ready-schema
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (sourceref) and rollback…
loom-database-design
Database schema and data model design for relational, NoSQL, time-series, and warehouse systems. Not for: event messaging.
loom-sql-optimization
Analyzes and optimizes SQL queries for performance.