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/jtsternberg/claude-plugins/dialnpx skills add jtsternberg/claude-plugins --skill dialgit clone --depth 1 https://github.com/jtsternberg/claude-pluginsWrote 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/jtsternberg/claude-plugins/dial)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/dial"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/dial.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.00056 | $0.09601 |
| Opus 5 | $0.00028 | $0.04800 |
| Sonnet 5 | $0.00011 | $0.01920 |
| Haiku 4.5 | $0.00006 | $0.00960 |
Grade D, and why
hotline-dial scanned grade D with 2 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Set these in `~/.claude/settings.json`'s `"env"` block or the shell: Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Clean up when the exchange is done: `rm -rf "$CALL_DIR"`. How it starts
The opening of the file, as written. The whole thing — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotline: Dial
Dial another workspace to ask questions, delegate work, or collaborate.
dial.sh does the plumbing — identity, resolution, transport choice, session
cache, launch, boot wait — in one command and hands back one JSON object.
Your job is the judgment: which workspace, which mode, and what to do about the
status it returns.
Arguments
$0(optional): Workspace reference — a dirmap ID, path, session ID, or fuzzy name.$1+(optional): The task/question for the remote workspace.--headless: force the headless transport (claude -p) for this dial even when cmux is up. Debugging the headless path, A/B-ing transports, or wantingclaude -p's structured output. Costs programmatic-usage credit; the cmux default doesn't. →--headless--detached/--new-workspace: spawn the callee in a disconnected new workspace tab instead of a side-by-side surface. The tab auto-closes once the response is captured, so nothing is left to watch or clean up. →--placement detached--window <name|ref>: land the callee as a surface in a specific cmux window (find-or-create), for grouping workers by project. Awindow:<n>ref targets that window; a bare name reuses the window holding a workspace titled<name>. Wins over--detachedif both are given. →--window <name|ref>--herdr: host the callee as a herdr agent instead of a cmux surface — a persistent pane owned by the herdr server, so the callee survives a detach, a closed lid, or a dropped SSH session. That is the reason to ask for it: a long work order you do not want tied to the life of a window. Requires herdr running, here or — with--remotebelow — on another box. Takes any mode, includingconference, and either the side or detached placement (herdr splits a pane off yours for both). →--transport herdr--remote <ssh-target>: run the callee on another box — herdr splits a pane and starts claude there, and hotline reads its answer back over ssh. For work that belongs on that machine: its checkout, its GPU, its network. It selects herdr on its own (nothing else can host anywhere but here) and is detached by nature, so--remote <target>alone is the whole invocation. Needs a non-interactive ssh hop plus herdr and claude on that box; if any of that is missing the dial is an error, never a quiet local call. →--remote <ssh-target>
What ships with it
28 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.
- references/cmux-rpc.md 5.1 KB
- references/codex-caller.md 4.9 KB
- references/dirmap-fallback.md 694 B
- references/error-recovery.md 39 KB
- references/native-messaging.md 6.6 KB
- scripts/check-cmux.sh 1.0 KB runs code
- scripts/check-herdr.sh 5.8 KB runs code
- scripts/close-superseded-surface.sh 14 KB runs code
- scripts/cmux-call-async.sh 27 KB runs code
- scripts/cmux-call.sh 20 KB runs code
- scripts/cmux-paste.sh 33 KB runs code
- scripts/cmux-reuse-surface.sh 21 KB runs code
- scripts/dial.sh 93 KB runs code
- scripts/headless-call-async.sh 8.7 KB runs code
- scripts/headless-call.sh 6.1 KB runs code
- scripts/herdr-call-async.sh 21 KB runs code
- scripts/herdr-prompt.sh 23 KB runs code
- scripts/herdr-reuse-agent.sh 13 KB runs code
- scripts/open-window-surface.sh 10 KB runs code
- scripts/persist-call-meta.sh 1.9 KB runs code
- scripts/register-call.sh 5.1 KB runs code
- scripts/resolve-side-opener.sh 3.5 KB runs code
- scripts/resolve-workspace.sh 7.1 KB runs code
- scripts/session-cache.sh 9.9 KB runs code
- scripts/surface-ready.sh 6.2 KB runs code
- scripts/transcript-extract.sh 17 KB runs code
- scripts/wait-for-response.sh 63 KB runs code
- scripts/wait-for-session.sh 25 KB runs code
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.
- today Changed · +113 lines · +23 tokens per session e53bb2e1afa6
- today Changed · +130 lines b78730aa07ef
- 4d ago First seen · 336 lines · 33 tokens per session scan D 5498922efa63
hotline-dial is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 9,601 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, 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
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…