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 surveygit 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/survey)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/survey"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/survey/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/survey"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/survey.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.00034 | $0.00422 |
| Opus 5.5 | $0.00014 | $0.00169 |
| Sonnet 5.5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
blueprint-adopt-survey 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.
What it actually says
Measure what is there today
.blueprint/answers.json names the places chaff will watch (places, a folder or a file a line), what kind of
documents they are (kind) and whether a GitHub workflow is wanted (ci). The person may not be an engineer: say
what you do in plain words.
Change nothing in the repository: this step only measures. The person approves the setup before anything is written.
Measure
The kind maps to a genre in <usecase pack>/kinds.json. For each place, run
sh <base pack>/checks/chaff.sh <place> --genre <genre> --compact and count the warnings and errors, by rule. Read a
few of them: a rule that reports mostly what the documents do on purpose may be worth turning down in chaff.yaml
rather than shelving — say which, and why, for the person to decide at the gate.
Write .blueprint/adopt.json
{ "genre": "docs/manual", "findings": 2, "proposal": "chaff.yaml に genre と language を書き、今の 2 件を棚に上げる。" }
findings is the number of warnings and errors chaff reports on all the places together, as that genre, now; the
check measures it again. If the folder already has a chaff.yaml or a .chaff-baseline.json, say so in
proposal: the next step keeps what they hold.
Done when
node <usecase pack>/checks/adopt.mjs survey (with BLUEPRINT_BASE and BLUEPRINT_USECASE set to the pack folders
from your prompt) passes. It writes .blueprint/adopt.txt, what the person reads before anything 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.
- 24d ago Changed · -13 lines · +5 tokens per session 2081b7942ced
- 25d ago Changed · +5 lines 6719bd77e045
- 27d ago First seen · 44 lines · 29 tokens per session scan A f17c4e13c32e
blueprint-adopt-survey is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 422 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.