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 importgit 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)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/import"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/import/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"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/import.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.00030 | $0.00652 |
| Opus 5.5 | $0.00012 | $0.00261 |
| Sonnet 5.5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Move the records in
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, as the
collection stored them), and the files they point at are under .blueprint/source/files/, at the path the record
names.
- Add
yarn import-source <database path>. It opens that database the way the app does (so the migrations run), then, for every collection insource.json— the ones linked to first, so references have something to point at — inserts each record into its table. - Names follow the spec and the pack's
spec/conversion.md("表と列の名前"): the table is the collection's slug with-as_; a stored field's column is its key, unchanged. Convert as the table says: a boolean is0/1, a date stays its ISO text, arefkeeps the referenced primary key, atablefield's rows go to its child table. - A record's
image/filevalue is a path: copy the file from.blueprint/source/files/<path>todata/files/<path>and keep the path in the column. A file the source did not have is left out and reported. - Running it twice leaves the same rows (insert or replace by primary key; child rows replaced with their parent).
- A record that does not fit (a value the column refuses, a reference to nothing) is not dropped silently: the script stops and names the collection, the record's primary key and the field.
test/import.test.ts: import into a temporary database and read a record of each collection back.- Say in the README how the records were moved, and that
yarn import-source data/app.dbis what did it.
Done when the check passes: into a fresh temporary database, run twice, every collection has as many rows as it had
records, every stored field reads back equal to the source, every pointed-at file is in data/files/, and
yarn test passes.
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 · 40 lines · 30 tokens per session scan A 5229c93ae3af
blueprint-from-collection-import is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 652 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.