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 extractgit 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/extract)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/extract"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/extract/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/extract"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/extract.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.00040 | $0.01329 |
| Opus 5.5 | $0.00016 | $0.00532 |
| Sonnet 5.5 | $0.00008 | $0.00266 |
| Haiku 4.5 | $0.00004 | $0.00133 |
Grade A, and why
blueprint-verify-extract 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 24d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract the dates, times and amounts
.blueprint/answers.json names the documents (documents, one path per line), what kind they are (kind),
the year to use for dates written without one (year, may be empty) and what the person is worried about
(focus). Read every document in full, starting with focus.
This step only reads and copies values out. It does not judge whether anything is wrong. That is decided by
machine in the next step, so do not skip an entry because it looks wrong. A wrong weekday or a wrong total is
exactly what must be extracted as written. Change nothing in the repository: the documents stay exactly as
they are. Write only under .blueprint/. A person reads the table you write before the machine judges it, so a
missed event is theirs to catch.
Write .blueprint/facts.json
{
"events": [
{
"id": "day1-depart",
"date": "2026-10-01",
"weekday": "木",
"start": "09:00",
"end": "11:30",
"title": "東京駅から新大阪駅(のぞみ)",
"citation": { "source": "itinerary.md", "address": "h2.1", "quote": "10月1日(木)9:00 東京駅発 → 11:30 新大阪駅着" }
}
],
"amounts": [
{ "id": "hotel", "label": "宿泊費", "value": 24000, "unit": "円", "citation": { "source": "estimate.md", "address": "h2.2", "quote": "宿泊費 24,000円" } }
],
"totals": [
{ "id": "grand-total", "label": "合計", "value": 36000, "unit": "円", "parts": ["hotel", "train"], "citation": { "source": "estimate.md", "address": "h2.2", "quote": "合計 36,000円" } }
],
"products": [
{ "id": "hotel-line", "label": "宿泊費", "value": 24000, "unit": "円", "of": ["hotel-rate", "hotel-nights"], "citation": { "source": "estimate.md", "address": "h2.2", "quote": "宿泊費 12,000円 × 2泊 = 24,000円" } }
]
}
- One event per thing that happens at a time: a departure, a check-in, a meeting. Keep them in the order the document gives them, because the next step reads that order as the intended sequence.
dateisYYYY-MM-DD. When the document omits the year, useyearfrom the answers. If that is empty too, write the date asMM-DD("10-01") and give it noweekday: a weekday without a year cannot be checked, and the check refuses one.weekdayis copied as written (「木」「(木)」「Thu」). Leave it out when the document gives none. Never add one the document does not have, and never correct one.start/endareHH:MM, 24-hour. Leave out what the document does not say. A range that writes AM/PM once covers both times:1:00–5:00 PMis 13:00–17:00,午後1時〜5時is 13:00–17:00.amountsare the lines that add up;totalsare the lines that claim to be their sum (合計, 小計, Total), withpartsnaming the amount ids they add up. A subtotal that is itself part of a grand total is both: list it as an amount too, under another id, and name that id in the grand total'sparts.productsare the lines that claim to be a product: a line's amount that is its unit price times its quantity (単価 × 数量), a tax that is a subtotal times a rate.ofnames the amount ids multiplied, two or more: the price and the quantity (unit台, 泊, 個, pcs — as written), or the subtotal and the rate (value10,unit%). Like a subtotal, a line that is also added into a total is listed as an amount too, under another id. Extract a product only where the document gives every factor; a line with no quantity written is not one.valueis a plain number (24000, not"24,000円");unitis the currency or unit as written (円, USD).id: lower-case letters, digits and-, unique across the whole file.citation.quoteis copied character for character from the document and must contain every value of its entry: the month and day, the weekday, each time, the amount. A quote may run over a line break (for a date in a heading above the times, quote from the heading through the line).addressuseschaff tree's addresses (sh <base pack>/checks/chaff.sh tree <document>).
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.
- 24d ago Changed · +8 lines 8381ad726709
- 25d ago Changed · +1 lines e0a8550d182a
- 26d ago First seen · 65 lines · 40 tokens per session scan A accf786e6c60
blueprint-verify-extract is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,329 once invoked, about $0.0002 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-29.
Other skills, from other repositories
moai-docs-generation
Documentation generation patterns for technical specs, API docs, user guides, and knowledge bases using real tools like Sphinx, MkDocs, TypeDoc, and Nextra. Use when creating docs from code, building doc sites, or automating documentation workflows.
moai-domain-html-report
Markdown-to-single-file-HTML report renderer. Six modes (status, incident, plan, explainer, financial, pr) selected by report type, crossed with three audience tiers (expert, basic, learn) derived from the active output style. The basic and learn tiers enrich the HTML with mermaid flowcharts, worked examples, and…
ase-docs-proofread
Analyze the documents for spelling, capitalization, punctuation, word break, or grammar errors. Use when the user wants to "proofread" or "spellcheck" a document.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
gdoc
Read publicly shared Google Docs using curl to download into a file.
atelier-setup
Configure a repository for Atelier's development workflow. Use only when explicitly invoked; inspect existing guidance, issue-tracker and domain-document conventions, preview the proposed configuration, and write only after approval. It does not install Atelier or initialize external tooling.