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 outlinegit 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/outline)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/outline"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/outline/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/outline"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/outline.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.00031 | $0.00361 |
| Opus 5.5 | $0.00012 | $0.00144 |
| Sonnet 5.5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
blueprint-write-outline 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 27d 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 outline
The person approved the brief. Now decide the parts, in .blueprint/outline.json:
{ "parts": [
{ "id": "intro", "title": "はじめに", "file": "guide/01-intro.md", "points": ["何のための手引きか", "読み方"], "length": "800 字", "status": "todo" }
] }
- How many parts. A short piece is one part, one file. A long document is a part per chapter or section, each its own file, so each round writes and checks one of them. A book: a part per chapter.
- Every key point of the brief lands in some part's
points. A point nobody owns is a point the document will miss. - Files are new. Choose paths that do not exist yet: the check refuses an outline that would overwrite
a file the person already has. Keep them inside this folder, outside
.blueprint/. - The order is the reading order, and
ids are short lowercase words (intro,ch-02-setup). - Every part starts as
"todo".
Write nothing else in this step. The person reads the outline and approves it before any part is written.
Done when
node <usecase pack>/checks/parts.mjs outline (with BLUEPRINT_BASE and BLUEPRINT_USECASE set to the
pack folders from your prompt) 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.
- 27d ago First seen · 31 lines · 31 tokens per session scan A 7fbdb608b077
blueprint-write-outline is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 361 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-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
self-assessment
Interactive skill assessment with personalized learning path generation.
project-design
Roteador de processos de design e marca que carrega orientações para criar arquivos DESIGN.md completos para um projeto e suas aplicações de interface.
loom-swift
Swift language expertise for idiomatic, production-quality code.
loom-usage
Meta-orchestration skill for Claude driving loom itself.
loom-c
C language expertise (C11/C17/C23) for memory-safe, portable, production-quality systems code.