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-production-cloudflaregit 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-production-cloudflare)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/import-production-cloudflare"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/import-production-cloudflare/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-production-cloudflare"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/import-production-cloudflare.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.00397 |
| Opus 5.5 | $0.00013 | $0.00159 |
| Sonnet 5.5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
blueprint-from-collection-import-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 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.
What it actually says
Move the records into production
This step's gates are deploy-production and credential: the user has approved writing the copied records into
their Cloudflare account, signed in with their own wrangler login. If .blueprint/source/source.json says records
is false, there is nothing to do: stop.
yarn wrangler whoami. If not signed in, ask the person, through the blueprint question tool, to runyarn wrangler loginin this folder themselves and tell you when it is done. Never handle an API token.- Run
yarn import-source --remote— the same import the local step proved. Do not change it here; if it fails, say why and stop. The publish step already created the database, applied the migrations and created the bucketwrangler.jsoncbinds. - Tell the person how many records went into each table, and how many files into the bucket.
Done when the check passes: the production D1, read back through wrangler, has every record with every stored field
equal to the source, and every pointed-at file is in the R2 bucket named in .blueprint/r2-bucket with the source's
bytes.
Always
- Read
.blueprint/spec.mdfirst. 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.
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 · 30 lines · 33 tokens per session scan A 2e84556b015a
blueprint-from-collection-import-production 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 397 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.