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/xuzhougeng/wispterm/wispterm-diagnosticsnpx skills add xuzhougeng/wispterm --skill wispterm-diagnosticsgit clone --depth 1 https://github.com/xuzhougeng/wisptermWrote 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/xuzhougeng/wispterm/wispterm-diagnostics)<a href="https://agentmods.dev/skills/xuzhougeng/wispterm/wispterm-diagnostics"><img src="https://agentmods.dev/badge/skills/xuzhougeng/wispterm/wispterm-diagnostics.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.1 | $0.00088 | $0.03005 |
| Opus 5 | $0.00044 | $0.01503 |
| Sonnet 5 | $0.00018 | $0.00601 |
| Haiku 4.5 | $0.00009 | $0.00300 |
Grade A, and why
wispterm-diagnostics 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 6d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WispTerm Diagnostics
Overview
Generate a safe, copyable Markdown diagnostic report for users filing WispTerm
issues. On Windows, installed WispTerm release packages include this plugin,
so the preferred user-facing path is to ask the user to invoke
$wispterm-diagnostics from WispTerm's AI Chat or Copilot and include their
symptoms/reproduction steps. The skill then uses the bundled PowerShell script
to collect WispTerm, Windows, OpenSSH, WebView2, bundled ConPTY, GPU, logs, and
config details. Do not ask Windows users to find a source checkout first.
On macOS, there is no equivalent script yet — use the manual bash workflow in the macOS section below.
Windows Workflow
- If a user needs instructions, tell them to open a WispTerm AI Chat tab or Copilot sidebar and send a request like:
$wispterm-diagnostics
Problem type: ssh-disconnect
Symptom: SSH Profile disconnects after 5-10 minutes idle with "Connection reset".
Repro steps: connect to the saved SSH profile, leave it idle, then run ls.
What I already tried: external ssh.exe with ServerAliveInterval works.
- Infer
-ProblemTypefrom the user's text. If it is unclear, useotherand keep the user's symptom/repro text in the generated issue draft. - Run the script from this skill directory as the implementation detail:
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\collect_wispterm_diagnostics.ps1 -ProblemType "other"
Use pwsh instead of powershell only if Windows PowerShell is unavailable.
Recommended labels: startup/crash, rendering/DPI, high-cpu,
keyboard/input, selection/copy/scrolling, SSH/SCP,
ssh-image-preview, html-preview, ssh-disconnect, file explorer,
WebView2/browser panel, updater, remote console, other.
- For rendering/DPI/multi-monitor glitch reports, first check whether
render-diagnostic.logis already present. If not, ask the user to addwispterm-debug-render = trueto their config (pressCtrl+,to open it), restart WispTerm, reproduce the glitch, then run the script. The log is written to%APPDATA%\wispterm\render-diagnostic.log.
What ships with it
2 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.
- 6d ago First seen · 287 lines · 88 tokens per session scan A 1b8404e53458
wispterm-diagnostics is a skill published in the GitHub repository xuzhougeng/wispterm (402 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 3,005 once invoked, about $0.0004 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
liney-cli
Use the Liney CLI (liney) to inspect or control a running Liney terminal workspace and the agent sessions it hosts. Liney runs several coding agents in parallel, each in its own pane/tab/worktree, so reach for this whenever the user wants to act on a pane other than the current one — check on, coordinate, read from…
terminal-setup-install
Idempotent macOS terminal installer for Ghostty, Oh My Zsh, Powerlevel10k, Glow, MesloLGS Nerd Font, plus optional markdown preview and clickable-path extras.
computer-use
Use Orca's computer-use CLI for OS/window-level inspection and input in visible local app windows. Use when a task must read or operate a native app or an external browser window (for example, Chrome, Edge, or Safari) or an app webview. Do not use for Orca's embedded browser or page-only browser automation. Use…
linear-tickets
Use Orca's Linear CLI through orca linear ... commands to read linked ticket context with orca linear issue --current --full --json, post completion updates, move work forward through Linear workflow states, attach PR/MR links with orca linear attach --current --url --title "PR/MR link" --json, and triage Linear tasks…
orca-cli
Use the public orca CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude…
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…