blueprint-summarize-summarize

blueprint-summarize-summarize is a skill for Claude Code, Codex from receptron/mulmoterminal. It costs 54 tokens per session (725 once invoked), scanned A, original, MIT.

A document-summary procedure that writes a cited summary to a project directory without changing the source documents. It reads the named documents in full and connects each sentence to supporting quotations or explains why a part was omitted.

In plain words
What is it for?
Use it to summarise documents to an agreed length for a specified reader and focus, with citations saved in `.blueprint/summary.json`.
Why use it?
It makes summaries traceable, so readers can check where each statement came from. It also prevents important sections from disappearing without an explicit reason.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to summarise documents to an agreed length for a specified reader and focus, with citations saved in .blueprint/summary.json.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/receptron/mulmoterminal/summarize
Install

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.

Any agent
npx skills add receptron/mulmoterminal --skill summarize
Clone the repo
git clone --depth 1 https://github.com/receptron/mulmoterminal

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for blueprint-summarize-summarize

README.md
[![agentmods](https://agentmods.dev/badge/skills/receptron/mulmoterminal/summarize/github.svg)](https://agentmods.dev/skills/receptron/mulmoterminal/summarize)
Your own site
<a href="https://agentmods.dev/skills/receptron/mulmoterminal/summarize"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/summarize/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.

agentmods 80×15 button for blueprint-summarize-summarize

Your own site · 80×15
<a href="https://agentmods.dev/skills/receptron/mulmoterminal/summarize"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/summarize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 725 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00725
Opus 5.5 $0.00022 $0.00290
Sonnet 5.5 $0.00011 $0.00145
Haiku 4.5 $0.00005 $0.00072

Measured 24d ago against content hash b4005407f979, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blueprint-summarize-summarize 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.

blueprints/summarize/skills/summarize/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Summarize, sentence by sentence

.blueprint/answers.json names the documents (documents, one path per line), how long the summary may be (length), who reads it (reader, may be empty) and what they most want to know (focus, may be empty). Read every document in full. The person may not be an engineer: say what you do in plain words.

Change nothing in the repository: the documents stay exactly as they are. Write only under .blueprint/.

The parts a summary answers for

Run sh <base pack>/checks/chaff.sh tree <file> --format json on each document. Its parts are its articles (kind article) when it has any; otherwise its sections at the first level with more than one (under a single title heading, the sections below it). Every part is either cited by some sentence of the summary or left out on purpose, with a reason the person can judge — never dropped silently.

Write .blueprint/summary.json

{
  "sentences": [
    {
      "text": "経理部の確認が済んだ申請は、毎月25日に給与口座へ振り込まれる。",
      "citations": [{ "source": "keihi.md", "address": "h1.3", "quote": "毎月25日にまとめて給与口座へ振り込みます" }]
    }
  ],
  "omitted": [{ "source": "keihi.md", "address": "h1.4", "why": "例外の手続きで、この読み手には要らないため" }]
}
  • One claim a sentence, in the reader's language and plain words, in the order that serves the reader — focus first when it names something.
  • Every sentence has at least one quotation that says what the sentence says: source as documents names it, address from the tree (the paragraph or item the words are in, or the part itself), quote copied character for character. The check runs chaff cite on every one.
  • A number is copied, never made. Every number a sentence states must appear in one of its quotations (or in the name of a place it cites, such as 第4条): the check refuses any other. Do not add up, convert or round.
  • The length is the most sentences length allows (短く 5, ふつう 10; くわしく has no limit). When the parts outnumber the sentences, one sentence may cite several parts, or a part the reader does not need may be left out in omitted — with a reason.

Read the full file on GitHub · 51 lines

Changes

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.

  1. 24d ago First seen · 51 lines · 54 tokens per session scan A b4005407f979

Subscribe to this mod's changes

blueprint-summarize-summarize is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 725 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.

Related

Other skills, from other repositories