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 termio-sh/termio --skill termio-devicegit 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-device)<a href="https://agentmods.dev/skills/termio-sh/termio/termio-device"><img src="https://agentmods.dev/badge/skills/termio-sh/termio/termio-device/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/termio-sh/termio/termio-device"><img src="https://agentmods.dev/badge/skills/termio-sh/termio/termio-device.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.00099 | $0.00758 |
| Opus 5.5 | $0.00040 | $0.00303 |
| Sonnet 5.5 | $0.00020 | $0.00152 |
| Haiku 4.5 | $0.00010 | $0.00076 |
Grade A, and why
termio 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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving sibling sessions (termiod)
If TERMIOD_SESSION_ID is not set in your environment, you are not running
inside a termiod session — say so and stop instead of trying to drive sessions
you cannot see.
You are running inside a session hosted by termiod on this machine, alongside
other sessions on the same host. Coordinate with them through the termiod
CLI. The installed CLI is the authority on syntax: where this text and
termiod --help disagree, trust the CLI.
Sessions here are scoped to this machine, not to a project. The daemon lists every session it hosts, so read the names and working directories before acting on one — there is no project filter to lean on.
termiod list --json— every session on this host, with its status (working/idle/needs_you/done/failed/unknown), name, and pid. Sessions are addressed by id or by name; both work everywhere a target is taken.termiod send <target> "<text>"— type into a session as if the user had. Use it to answer a sibling that is blocked on a question.--no-entertypes the text without pressing Enter.termiod create --name <name> --cwd <dir> -- <program> [args…]— start a new session and print its id. With no--argv it starts a login shell.termiod kill <target>— kill a session and its process group.termiod set-status "$TERMIOD_SESSION_ID" <state>— report your own state. Valid states areworking,idle,needs_you,done,failed, andunknown.--title "<short label>"sets the label a viewer shows beside the session.
When to use this
- Delegating. A task that is genuinely separate work — a long build, an independent investigation — can go to a new session so the user watches it in its own pane.
- Supervising. Before reporting that something is done, check whether a
sibling you started is still
workingor has goneneeds_you. - Unblocking. A sibling sitting at
needs_youis waiting on a human. If you can answer it from what you already know,sendthe answer.
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.
- 1mo ago First seen · 56 lines · 99 tokens per session scan A 738b58c0fc7b
termio is a skill published in the GitHub repository termio-sh/termio (548 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 758 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.