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 reportgit 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/report)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/report"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/report/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/report"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/report.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.00024 | $0.00496 |
| Opus 5.5 | $0.00010 | $0.00198 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
blueprint-compare-report 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.
What it actually says
The comparison table
.blueprint/comparison.json is the pairing the person approved. Write .blueprint/compare-report.md for them,
in their language and in plain words:
-
## 新旧対照表/## Comparison table— one row per pair that is notsame, in the order of the new version (a removed article where it stood in the old one): the old article, the new article, and what changed. Name each article as the document does (第4条,Article 4), and quote the words or numbers that differ from each version. A Markdown table works well:旧 新 変わったこと 第4条（委託料と支払） 第4条（委託料と支払） 月額「200,000円」→「220,000円」 （なし） 第5条（報告） 足された: 毎月5日までに前月の報告書を納める The check looks for every changed, added and removed article's name in this section.
-
A line after the table on the articles that are the same, including those that only moved or were renumbered (「旧第9条は新第8条になった。中身は同じ」).
-
## 確かめたこと/## What was checked— that every article of both versions is in one pair; that whether each pair changed was decided by comparing the text by machine, not by reading; that neither document was changed. Say what was not checked: a change's effect on other articles that refer to it (a renumbered article that other articles still cite by its old number), and anything outside the articles (the title, the preamble).
When focus names something, put the pairs that touch it first under the table's heading, and say so.
Done when
node <usecase pack>/checks/report.mjs (with BLUEPRINT_BASE and BLUEPRINT_USECASE set) 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.
- 24d ago Changed · -3 lines · +1 tokens per session da87a029ab59
- 25d ago Changed · +2 lines f187eafdef04
- 26d ago Changed · +18 lines d9ca27ce0515
- 27d ago First seen · 17 lines · 23 tokens per session scan A 45419f73d8e4
blueprint-compare-report is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 496 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.
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.