Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/hlh2023/terminal-use-mcp/terminal-use)<a href="https://agentmods.dev/skills/hlh2023/terminal-use-mcp/terminal-use"><img src="https://agentmods.dev/badge/skills/hlh2023/terminal-use-mcp/terminal-use/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/hlh2023/terminal-use-mcp/terminal-use"><img src="https://agentmods.dev/badge/skills/hlh2023/terminal-use-mcp/terminal-use.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.00026 | $0.09550 |
| Opus 5 | $0.00013 | $0.04775 |
| Sonnet 5 | $0.00005 | $0.01910 |
| Haiku 4.5 | $0.00003 | $0.00955 |
Grade C, and why
terminal-use scanned grade C 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `Allow command: rm -rf /?` → ASK USER How it starts
The opening of the file, as written. The whole thing — 886 lines — stays where its author put it; the contents beside it link to each section on GitHub.
terminal-use: Terminal Control Skill
terminal-use-mcp v0.2.0 — This skill is maintained alongside the MCP server. Version check: call
terminal.health→ compare theversionfield with this header. If server version > skill version, prompt the user to update (npx skills updateor re-download from GitHub). Full versioning details in theterminal-use-setupskill.
Terminal computer use — control interactive TUI programs that require keyboard input. This is NOT a shell runner. Use your bash tool for simple commands.
Customization Guide
This skill is designed to be trimmed to your needs. Each section is self-contained — delete any sections you don't need to reduce token consumption.
| Section | Content | Safe to Remove? |
|---|---|---|
| Pre-flight Check | Version/provider check before first use | ⚠️ Keep — prevents errors from server mismatch or outdated skill |
| §1 What This Tool Is For | Purpose, when to use/not use | ⚠️ Keep — essential for correct tool usage |
| §2 Provider Selection | native-pty vs tmux choice, provider availability | ✅ Remove if you always use native-pty |
| §3 Standard Operation Loop | Core workflow (snapshot → act → wait) | ⚠️ Keep — critical for correct operation |
| §4 Tool Quick Reference | Parameter tables for all available tools | ✅ Remove if your AI already knows the tool schemas |
| §5 Available Key Names | Key name list | ✅ Remove — AI can call terminal.keys instead |
| §6 Safety Rules | 6 non-negotiable safety rules | ⚠️ Keep — prevents credential exposure and data loss |
| §7 Common Patterns | 7 usage patterns with examples | ✅ Remove largest section (~130 lines) if your AI learns by doing |
| §8 Snapshot Structure | Response JSON fields | ✅ Remove — AI can discover from tool output |
| §9 Error Handling | Error code reference table | ✅ Remove — AI can handle errors reactively |
| §10 Configuration & Setup | Reference to terminal-use-setup skill |
✅ Remove if terminal-use-setup skill is installed |
| §11 Checklist | Pre-use decision checklist | ✅ Remove if your AI follows §3 loop reliably |
| §12 Remote Terminal Control | When to use remote, ACP vs SSH, provider selection | ✅ Remove if you only use local terminals |
| §13 Remote Safety Rules | 10 non-negotiable remote safety rules | ✅ Remove if you only use local terminals (but ⚠️ keep if using remote) |
| §14 Remote Tools Reference | targets / target_info / verify_target details | ✅ Remove — AI can discover from tool schemas |
| §15 Remote Error Codes | SSH-specific error code table | ✅ Remove — AI can handle errors reactively |
| §16 Remote Operation Patterns | 5 remote usage patterns with examples | ✅ Remove largest section (~150 lines) if your AI learns by doing |
| §17 Remote Configuration | Reference to terminal-use-setup skill |
✅ Remove if terminal-use-setup skill is installed |
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.
- 10d ago First seen · 886 lines · 26 tokens per session scan C 616f69c23351
terminal-use is a skill published in the GitHub repository HLH2023/terminal-use-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 9,550 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
axstream
Fast deterministic macOS UI automation via replayable macros. Use BEFORE driving any macOS app's UI by hand (clicking/typing via computer-use or screenshots) — if a macro exists, replay finishes the task in seconds with no per-step reasoning; after doing a UI task manually, save it as a macro so the next run is fast.…
thread-cron
Design and operate native thread-local cron jobs for a cron-enabled Codex CLI build.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. Use when the user asks about notes, vault management, PKM, knowledge base organization, wikilinks, or personal knowledge management in Obsidian.