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 mulmoterminal-helpgit 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/mulmoterminal-help)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/mulmoterminal-help"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/mulmoterminal-help/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/mulmoterminal-help"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/mulmoterminal-help.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.00133 | $0.02516 |
| Opus 5.5 | $0.00053 | $0.01006 |
| Sonnet 5.5 | $0.00027 | $0.00503 |
| Haiku 4.5 | $0.00013 | $0.00252 |
Grade A, and why
mulmoterminal-help scanned grade A with 1 finding 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --noproxy localhost -s "http://localhost:${MULMOTERMINAL_PORT:-34567}/api/help/sources" How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MulmoTerminal — ask anything about it
Every answer is read, not remembered. The guide, the changelog, the source and the running server are on this machine; a sentence that none of them backs is a guess, and a guess about a button that does not exist costs the user longer than "I could not find that". This skill exists so the person asking gets the behaviour of the version they are running, in their own language, with the place it was checked.
Rules that hold in every answer
- Never answer from memory. Read the file or call the route, then answer. A general knowledge of terminals, Claude Code or similar apps is not evidence about MulmoTerminal.
- Name where you checked — a guide page, a source file, a route — in one short line after the answer. The user can follow it, and it is how a wrong answer gets caught.
- Say which version you are describing. The running version comes from the server (below). A newer release may exist; its features are not on this machine and must be introduced as "after you update", never as something the user can click now.
- The source wins over the guide. When a page and the implementation disagree, say the page is behind and answer from the code. When two pages disagree, the newer dated page wins.
- "Not found" is an answer. If nothing shipped describes it, say so and offer to look at the source or to ask in the project's Discussions. Do not fill the gap with what would be plausible.
- Change nothing. This skill reads. A user who wants a setting changed is handed to the skill that
owns it (last section); a user whose app misbehaves is handed to
mulmoterminal-bug-report. - Reply in the user's language. Japanese readers get the
jaguide; every other language readsen(that is also what the app does). Quote UI words as the user's interface shows them. - Short answers, one question at a time. Lead with the answer, then how to get there, then the pointer. Offer the published page when the topic is wide.
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.
- 13d ago First seen · 149 lines · 133 tokens per session scan A df03f74bc98d
mulmoterminal-help is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 133 tokens to every session and 2,516 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-11.
Other skills, from other repositories
refit
Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
subscription-setup
A setup workflow for creating recurring medical-learning subscriptions after a doctor’s profile has been registered.
study-plan
Build a weekly and daily study schedule from the goal and the available time, with method notes and adjustment rules, delivered as an Excel workbook.
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…
model-prompt-pack
Use when asked to write prompts for image-to-3D or text-to-3D tools, generate 3D models of a topic's parts, plan the assets for a 3D explorer, or build a labelled parts list with sources. Produces prompts for image-to-3D tools, one per object, plus a parts list for labelling in which every label names a trusted…