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-bug-reportgit 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-bug-report)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/mulmoterminal-bug-report"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/mulmoterminal-bug-report/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-bug-report"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/mulmoterminal-bug-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00126 | $0.01664 |
| Opus 5 | $0.00063 | $0.00832 |
| Sonnet 5 | $0.00025 | $0.00333 |
| Haiku 4.5 | $0.00013 | $0.00166 |
Grade A, and why
mulmoterminal-bug-report 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 12d 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.
- the running server: `curl -s http://localhost:34567/api/config` (34567 is the default port; How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MulmoTerminal — is it a bug?
The goal is that the user ends up unblocked, not that an issue gets filed. An issue is what's left after the other three steps fail to explain the behaviour.
Work the steps in order. Stop the moment the user is unblocked.
Rules that hold in every step
- Never assert "that's by design" from memory. Say it only with a reason attached: a config key,
an implementation file, a guide page.
faq.mdis an index of where to look — it deliberately contains no values. - Read the real thing. Current and default values come from the user's actual config file, the schema in the source, or the running server — never from this file, and never from recollection.
- "I don't know" is an allowed answer. If a step cannot decide, say so and go to the next one. Never close the conversation by guessing.
- Nothing leaves the machine before the user has seen it in full and said yes.
- Reply in the language the user writes in.
Step 1 — Hear the symptom (collect nothing yet)
Ask with AskUserQuestion, options first — a user who is already frustrated should be picking, not
composing. Up to 4 questions per call; two calls cover this comfortably.
- What kind — display looks wrong / input doesn't work / a session died or won't connect / won't start at all / phone features / something else
- Where — a grid cell / the zoomed view / the single view / the file browser / settings / phone
- Which agent — claude / codex / shell / a launcher cell / a command cell
- How often — every time / sometimes / once
- Since when — after an update / it always did this / not sure
Then, in prose: what did you expect, and what happened instead? Those two sentences are what the next step is judged against, so get them before touching anything else.
Step 2 — Is it configuration, or by design? (this is the actual job)
- Read
faq.md(next to this file) and find the entry closest to the symptom. - Follow its pointers to the real values:
- global config:
~/.mulmoterminal/config.json - directory config:
<the directory in question>/.mulmoterminal.json - the running server:
curl -s http://localhost:34567/api/config(34567 is the default port; if the user changed it, it's the port in their browser's address bar)./api/update-status,/api/sessions,/api/git-status?cwd=<dir>and/api/dir-config?cwd=<dir>answer too. - the source files named by the entry, when the question is about accepted values or behaviour
- global config:
- If that explains the gap between expected and actual, say why, show the fix, and stop.
- If the fix is a
.mulmoterminal.json, hand off to/mulmoterminal-configinstead of dictating JSON — it knows the schema and validates.
- If the fix is a
- If nothing explains it, or the explanation is a guess, go to Step 3. Do not stretch the FAQ to cover a symptom it doesn't cover.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 135 lines · 126 tokens per session scan A 3a7b2a6ad895
mulmoterminal-bug-report is a skill published in the GitHub repository receptron/mulmoterminal (212 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,664 once invoked, about $0.0006 per session on Opus 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-08-30.
Other skills, from other repositories
dev-doctor
Run a development-focused health check on the AIWG repository structure.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
aiwg-doctor
Run a comprehensive health check on the AIWG installation and workspace with pass/fail diagnostics and remediation steps.
browser-doctor
Read-only health check on browser-control setup. Verifies browser binary, Playwright MCP Bridge extension presence, token file mode/contents, AIWG MCP registration, provider config injection, and optional workspace allow-list. Outputs pass/fail per check with remediation commands.
debug-memory
Query and manage the executable feedback debug memory.
fix
Fix issues end-to-end across data pipelines (Airflow/dbt), app stack (backend/frontend), and infra (CI/CD, Terraform, K8s). Scout → diagnose → apply at root cause → verify with fresh evidence → add regression guard. Use for failing DAGs, dbt test failures, 5xx, UI regressions, GH Actions failures, terraform drift…