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-html-plangit 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-html-plan)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/mulmoterminal-html-plan"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/mulmoterminal-html-plan/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-html-plan"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/mulmoterminal-html-plan.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.00155 | $0.01663 |
| Opus 5.5 | $0.00062 | $0.00665 |
| Sonnet 5.5 | $0.00031 | $0.00333 |
| Haiku 4.5 | $0.00015 | $0.00166 |
Grade A, and why
mulmoterminal-html-plan 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 2d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan in HTML, let the user decide, take the result back
A text plan asks the user to imagine the options. A page shows them. The point of this skill is the round trip: you lay out the plan, the user tries the choices and settles them on the page, and their decisions come back to you as a message you can act on. You do not ask the questions one by one in the terminal; the page asks them all at once, where they can be seen side by side.
1. Know what you are planning before you draw anything
Read the request, the code it touches and the project's own instructions (CLAUDE.md, AGENTS.md,
existing plans). Then sort everything you know into three piles:
- Settled — the user said so, or the code leaves no choice.
- Assumed — your best reading, which the user may want to correct.
- Open — a real choice with more than one reasonable answer.
Only the third pile becomes controls on the page. If it is empty, you do not need this skill: write the plan and get on with it. Keep the user's words for what they asked; do not grow a small change into a strategy document.
2. Build one self-contained page
One HTML document, everything inline. What the page can and cannot do:
- Scripts and styles inline, or from the allowed CDNs (
cdn.jsdelivr.net,unpkg.com,cdnjs.cloudflare.com,cdn.plot.ly, Google Fonts). Anything else is blocked silently. - No
fetchor XHR. Connections from the page's own script are blocked, so put the data the page needs into it. Loading a library from those CDNs, and images or media overhttps:, still works. - No storage. The page runs in a sandbox with an opaque origin:
localStorageand cookies throw. Keep state in variables.
Shape it around the decisions, roughly in this order — leave out any part that has nothing in it:
- What this is — one or two sentences: the goal and what is out of scope.
- Settled — a short list, so the user can see you understood.
- Assumed — each assumption with a control to flip it (a checkbox, a "no, actually…" text box).
- Choices — one block per open question. Show the options, not just their names:
- a UI choice: render each option as a small live mockup (real labels, real data shape, no lorem ipsum), side by side, with a radio to pick one;
- an API or data choice: the code or the JSON each option produces, side by side;
- an ordering or priority: a list the user can reorder;
- a number (a limit, a timeout, a size): a slider or input with the consequence shown next to it. Say what each option costs in one line. Mark your recommendation, and preselect it.
- Steps — the implementation sequence, only where the order is real. Let it react to the choices above when they change the steps.
- Risks — only ones you can name concretely.
- What will be sent — a live summary of every decision as it stands, updated as the user clicks, so nothing is sent that they have not seen.
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.
- 2d ago Changed · +9 lines 0be2b5920516
- 3d ago First seen · 105 lines · 155 tokens per session scan A 2c317cbf5ac2
mulmoterminal-html-plan is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session and 1,663 once invoked, about $0.0006 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-22.
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.