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/deepgram/wsh/core-mcpnpx skills add deepgram/wsh --skill core-mcpgit clone --depth 1 https://github.com/deepgram/wshWrote 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/deepgram/wsh/core-mcp)<a href="https://agentmods.dev/skills/deepgram/wsh/core-mcp"><img src="https://agentmods.dev/badge/skills/deepgram/wsh/core-mcp.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.00076 | $0.04126 |
| Opus 5 | $0.00038 | $0.02063 |
| Sonnet 5 | $0.00015 | $0.00825 |
| Haiku 4.5 | $0.00008 | $0.00413 |
Grade A, and why
core-mcp 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 4d 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.
curl examples and a bootstrap sequence. How it starts
The opening of the file, as written. The whole thing — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wsh: Terminal as a Service (MCP)
You have access to wsh via MCP tools that give you direct control over
terminal sessions. You can see exactly what's on screen, send
keystrokes, wait for commands to finish, and create visual elements —
all through MCP tool calls.
Think of it this way: wsh gives you eyes (read the screen), hands (send input), patience (wait for output to settle), and a voice (overlays and panels to communicate with the human).
How It Works
wsh manages terminal sessions via a server daemon that listens on a
Unix domain socket (by default at ${XDG_RUNTIME_DIR}/wsh/default.http.sock).
MCP tools connect to this socket automatically. The human sees their
normal terminal. You interact through tool calls to the same session.
Everything is synchronized — input you send appears on their screen,
output they generate appears in your tool responses. All tools take a
session parameter to specify which session to operate on (e.g.,
"default").
Getting Started
Step 1: Verify you have MCP tools. Check your toolkit for tools
starting with wsh_ (e.g., wsh_send_input, wsh_get_screen,
wsh_create_session). If you have them, proceed to step 2.
If you do NOT have wsh_* tools, the MCP bridge is not running.
Do NOT try to start a server manually — that won't give you MCP tools.
Instead, fall back to the HTTP API: search your workspace for
skills/core/ and read SKILL.md. It has every endpoint with working
curl examples and a bootstrap sequence.
Step 2: Create a session. Sessions are where commands run:
wsh_create_session(name="work")
Returns the session name and terminal dimensions on success.
Step 3: Use the send/wait/read loop. The primary tool:
wsh_send_and_read(session="work", keys=[{"text": "ls -la"}, {"key": "enter"}], format="plain")
This sends keystrokes, waits for idle, and returns the screen in one call.
For more control, use wsh_send_input, wsh_await_idle, and
wsh_get_screen separately.
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.
- 4d ago First seen · 464 lines · 76 tokens per session scan A c37f2b7d1e20
core-mcp is a skill published in the GitHub repository deepgram/wsh (5 stars, last pushed 3mo ago), licensed ISC. It adds 76 tokens to every session and 4,126 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…