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 applygit 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/apply)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/apply"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/apply/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/apply"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/apply.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.00055 | $0.00746 |
| Opus 5.5 | $0.00022 | $0.00298 |
| Sonnet 5.5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
blueprint-adopt-apply 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set chaff up
The person approved the setup in .blueprint/adopt.json. The documents stay exactly as they are: fixing what is
shelved is 「文書を整える」's work, later.
1. chaff.yaml
Write the folder's chaff.yaml with the genre from .blueprint/adopt.json and the documents' language
(npx chaffjs init --genre <genre> writes a commented one). If the folder already has one, set its genre to the
chosen one and keep every other line it has — the check refuses any other line of the old file that is gone. Add the rule
levels the person agreed to at the gate, nothing else.
2. Shelve today's findings
Run sh <base pack>/checks/chaff.sh baseline <place> … with every place. It writes .chaff-baseline.json in the
folder: the findings there today are not reported again; new ones are. Tell the person to commit it with
chaff.yaml.
3. The workflow — only when ci is 「GitHub の PR に指摘を出すワークフローを作る」
Copy <usecase pack>/templates/chaff.yml to .github/workflows/chaff.yml, replacing {{PATHS}} with the places
separated by spaces, and change nothing else: the check compares the file with the template filled in that way, line
for line. Its permissions: let the workflow read the documents (contents: read) and upload findings
(security-events: write), nothing more. A place whose name has a space or a character a shell reads ($, ;, *,
quotes…) cannot go into the workflow: the interview refuses it, so ask the person to name a folder above it instead. When ci is 「作らない」, add nothing under .github/.
4. The report
Write .blueprint/adopt-report.md for the person, in their language and in plain words:
## 入れたもの/## What was set up—chaff.yaml(the genre, and why),.chaff-baseline.json, and the workflow.github/workflows/chaff.ymlwhen one was made. The check looks for each file's name.## 棚に上げた指摘/## Shelved findings— how many were shelved, by rule, in plain words.## これから/## From now on— only new findings are reported (runnpx chaffjs <places>by hand, or see them on the pull request's lines); how to lower the shelf later (「文書を整える」, thenchaff baselineagain); that the workflow needs code scanning enabled on the repository (a public repository has it; a private one needs GitHub Advanced Security).
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 · 48 lines · 55 tokens per session scan A 485b5f3d5c81
blueprint-adopt-apply is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 746 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
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
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-ref-secops
DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF…
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…
documentation-patterns
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.