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 keepgit 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/keep)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/keep"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/keep/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/keep"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/keep.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.00032 | $0.00296 |
| Opus 5.5 | $0.00013 | $0.00118 |
| Sonnet 5.5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
blueprint-ask-keep 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.
What it actually says
Keep the answers
The person has read the answers and approved them. Read .blueprint/answers.json and
.blueprint/replies.json.
Never change a document. The check compares each one with the fingerprint recorded when the answers were written.
If keep is 残さない（.blueprint の中だけ）, there is nothing to write: leave FAQ.md exactly as it is,
run the check and stop.
Otherwise add to FAQ.md in this folder (create it if there is none). Add after what it already holds;
never edit or reorder what is there — the check compares the beginning of the file with what it held
before. For each question: the question as a ## heading, word for word; the answer; and where it is
written (the document, and the place named as in the answer: 第4条第2項, or a section's heading in 「」 —
in an English FAQ, in "…" — never chaff's h1.3). For a question the documents do not answer, say so — that is worth keeping
too.
Done when
node <usecase pack>/checks/replies.mjs keep 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.
- 16d ago Changed · +1 lines a8fc109ff23e
- 18d ago First seen · 26 lines · 32 tokens per session scan A 871aab93f93b
blueprint-ask-keep is a skill published in the GitHub repository receptron/mulmoterminal (238 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 296 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.