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 agentmods add skills/termio-sh/termio/termio-bug-reportnpx skills add termio-sh/termio --skill termio-bug-reportgit clone --depth 1 https://github.com/termio-sh/termioWrote 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/termio-sh/termio/termio-bug-report)<a href="https://agentmods.dev/skills/termio-sh/termio/termio-bug-report"><img src="https://agentmods.dev/badge/skills/termio-sh/termio/termio-bug-report.svg" alt="Measured on agentmods" 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 | $0.00159 | $0.01891 |
| Opus 5 | $0.00079 | $0.00945 |
| Sonnet 5 | $0.00032 | $0.00378 |
| Haiku 4.5 | $0.00016 | $0.00189 |
Grade A, and why
termio-bug-report 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 5d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose a freeze, then file it
Two jobs, in this order: work out what actually broke, then turn that into an issue someone can act on. Skipping the first half produces "termio froze on my Mac", which no one can fix.
0. Before anything else: is it hung right now?
Ask this first, in one line, and wait for the answer.
If the app is currently beachballing, do not let the user force-quit it. The main-thread stack that explains the freeze exists only while the process is alive. Force-quitting destroys the single most valuable piece of evidence, and it cannot be recovered afterwards from any log.
Capture it immediately:
./skills/termio-bug-report/scripts/collect.sh --minutes 60
The script samples every live termio and termiod process first, before it touches
anything slower. It prints the bundle directory it created; everything below
works on that directory. It needs no privileges and never copies pair.token.
If the freeze is already over, run the same command — the crash, CPU-burn, and unified-log evidence survives it, only the live stack is gone.
1. Read the evidence
Read manifest.md first, then in this order — stopping as soon as something
explains the symptom:
reports/index.md— one line per crash / CPU-burn report macOS wrote. A crash here usually ends the investigation on its own.sample-*.txt— where each process's main thread actually is.environment.md— versions, running processes, agent CLIs, memory.unified-log-termio.txt— termio's own trail.unified-log-system.txt— what the system said about the process.daemon/tombstones.json— how sessions ended, when the complaint is "a session froze / vanished" rather than "the app froze".
references/signatures.md has the reading guide for each artifact and a table of
every prior termio hang and crash with its root cause. Read it before writing a
diagnosis — most reports match one of them, and naming the prior bug is worth
more than a fresh theory.
What ships with it
3 files 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.
- 5d ago First seen · 184 lines · 159 tokens per session scan A 629162594399
termio-bug-report is a skill published in the GitHub repository termio-sh/termio (395 stars, last pushed yesterday), licensed MIT. It adds 159 tokens to every session and 1,891 once invoked, about $0.0008 per session on Opus 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-08-30.
Other skills, from other repositories
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
frame-macos-notification
拟真 macOS 通知 banner + app icon + 标题正文, 适合 video overlay / 产品发布预告.
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
deck-pitch
10 页融资 deck, 白底 + 蓝紫渐变 hero, traction 柱状, $X.XM ask.