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 pairgit 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/pair)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/pair"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/pair/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/pair"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/pair.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.00046 | $0.00759 |
| Opus 5.5 | $0.00018 | $0.00304 |
| Sonnet 5.5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
blueprint-compare-pair 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair the articles of the two versions
.blueprint/answers.json names the old version (old), the new version (new) — one file each — and what the
person wants looked at first (focus, may be empty). Read both in full. The person may not be an engineer: say
what you do in plain words.
Change nothing in the repository: neither version is touched. Write only under .blueprint/.
Find the articles
Run sh <base pack>/checks/chaff.sh tree <file> --format json on each version. Every node whose kind is
article is one article; its address ("4") is how you name it below, and attrs.label (第4条,
Article 4) is how the person reads it. The check uses the same tree, so an article chaff does not read as one
is not yours to pair.
Pair them
For each article of the old version, find the article of the new version that carries the same provision — by
what it says, not by its number: a provision that moved or was renumbered (old 第9条 is new 第8条) is one pair.
Then write .blueprint/comparison.json:
{ "rows": [
{ "old": "1", "new": "1", "change": "same" },
{ "old": "4", "new": "4", "change": "changed", "what": "委託料が月額200,000円から220,000円になった" },
{ "old": null, "new": "5", "change": "added", "what": "毎月5日までの報告の条が足された" },
{ "old": "8", "new": null, "change": "removed", "what": "成果物の扱いの条が消えた" },
{ "old": "9", "new": "8", "change": "same" }
] }
same/changed— botholdandnew.changedneedswhat: one line, in the person's language, saying what is different, with the words or numbers from both versions. A change in a paragraph or an item is a change to the article that holds it.added— onlynew;removed— onlyold. Awhatsaying what the article is about helps the person.- Every article of each version appears in exactly one row.
Whether a pair is same or changed is not a judgement: the check compares the two articles' text (spacing
aside, and leaving out the article's own number) and refuses a same whose text differs and a changed whose
text does not. When you pair two articles that the check calls different but you think the change is trivial
(punctuation, a character's width), it is still changed: say so in what.
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 First seen · 52 lines · 46 tokens per session scan A 40d925f36e8a
blueprint-compare-pair is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 759 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-10-01.
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.