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 answergit 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/answer)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/answer"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/answer/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/answer"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/answer.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.00036 | $0.00870 |
| Opus 5.5 | $0.00014 | $0.00348 |
| Sonnet 5.5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
blueprint-ask-answer 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 16d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer from the documents
.blueprint/answers.json names the documents (documents, one path per line), the questions
(questions, one per line) and whether to keep the answers (keep). The person may not know the
documents well: answer in their language and in plain words.
Change nothing in the repository: this step only reads. Write only under .blueprint/; the person reads
the answers before anything is kept.
How to answer
- Only from the documents. Not from general knowledge, not from what such documents usually say. If the documents do not answer a question, the answer is that they do not — and what they do say nearby, if it helps.
- Find where it is written.
chaff tree <document>(through the base pack's wrapper,sh <base pack>/checks/chaff.sh tree <document>) shows the document's addresses — articles, sections, items — so an answer can say "第4条第2項" or "Section 3.1". Read the whole relevant part, including exceptions and definitions elsewhere that change its meaning. - When provisions disagree, say so and quote both rather than choosing one.
Write .blueprint/replies.json
{
"replies": [
{
"question": "委託料はいつまでに払う?",
"found": true,
"answer": "検収後30日以内です(第4条第2項)。",
"citations": [{ "source": "contract.txt", "address": "第4条第2項", "quote": "成果物の検収後30日以内に" }]
},
{
"question": "消費税は含まれる?",
"found": false,
"answer": "文書には書かれていません。第4条第1項は「金50万円」とだけ定めています。",
"citations": [{ "source": "contract.txt", "address": "第4条第1項", "quote": "委託料として金50万円を支払う" }],
"searched": ["消費税", "税", "税込", "税別"]
}
]
}
question: the question exactly as it is inquestions. One reply per question, none extra.found:truewhen the documents answer it. Then at least one citation.citations:sourceis the document's path asdocumentsnames it;addressis where;quoteis copied character for character — the check runschaff citeon every one. Name every cited place in theanswertext so the person can open the document there: an article or item as the document numbers it (第4条第2項, Section 3.1), and a section of a Markdown document by its heading, word for word, in 「」 (「作業用フォルダを信頼しておく」; in an English answer, "Getting started") — the check looks for it in those marks. chaff's index for a section (h1.3) goes inaddressonly — it means nothing to the person.searched: whenfoundisfalse, the words and places you looked for.
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.
- 16d ago Changed · +4 lines 422be81f97eb
- 18d ago First seen · 61 lines · 36 tokens per session scan A 16322c3fbd9d
blueprint-ask-answer is a skill published in the GitHub repository receptron/mulmoterminal (238 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 870 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.
ase-sync-export
Export the SpecBook-based specification (SPEC) into ready-to-consume renderings like HTML, PDF, normalized Markdown, or JSON. Use when the user wants to "export", "render", or "materialize" the specification.
ai-provider-claude-vision
Image understanding and document analysis with Claude's multimodal capabilities -- image input formats, PDF processing, multi-image patterns, structured extraction, and token cost estimation.
pdf-toolkit
Audit PDF files for metadata leakage, page count, encryption, JavaScript, embedded files, and version. Use before sending a PDF externally, when redacting sensitive metadata, or running a PDF security review.
pptx-toolkit
Audit PowerPoint (.pptx) decks for slide count, text density, embedded images and fonts, hidden slides, speaker notes, and animation density. Use when reviewing a board deck, sales deck, or conference talk before sending.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…