Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sjungling/sjungling-claude-plugins/plugin install workflowWrote 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/commands/sjungling/sjungling-claude-plugins/teleport-tmux)<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/teleport-tmux"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/teleport-tmux/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/commands/sjungling/sjungling-claude-plugins/teleport-tmux"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/teleport-tmux.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.00018 | $0.01111 |
| Opus 5 | $0.00009 | $0.00556 |
| Sonnet 5 | $0.00004 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
teleport-tmux 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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teleport this Claude conversation into a tmux window so the user can close the terminal they accidentally started Claude in without losing the session.
macOS cannot move a live process's controlling terminal (no working reptyr),
so this does NOT move the running process. Instead it arms a new tmux window to
resume the current conversation from disk (claude --resume <session-id>)
the moment the old process exits. The conversation transcript is persisted per
turn, so everything committed transfers; only truly in-flight work is lost.
All the real work lives in ${CLAUDE_PLUGIN_ROOT}/scripts/teleport-tmux.sh.
This command just runs it in two phases and relays the result.
IMPORTANT — run every bash block in this command with the sandbox DISABLED (
dangerouslyDisableSandbox: true). tmux talks to its server over a Unix socket (e.g./private/tmp/tmux-501/default) that lives outside the default sandbox's writable allowlist. Under the sandbox,tmux list-sessions,new-window, andsend-keysall fail witherror connecting to … (Operation not permitted). The script surfaces this asERROR_LISTING_SESSIONSinstead of silently hiding sessions — but it still cannot create the window unless the sandbox is off. Thecommand -v tmuxcheck passes either way (the binary exists), so the failure is easy to miss. Disable the sandbox up front.
Follow this workflow exactly.
Step 1: Discover state
Run this (sandbox disabled) and read its output:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/teleport-tmux.sh" --discover
Capture from the output:
RESUME_SCRIPT— path passed to--armin Step 3.AUTO—yesif the oldclaudePID was detected,nootherwise.INSIDE_TMUX—yesif we're already inside tmux.- The session list under
--- existing tmux sessions ---.
If you see ERROR_LISTING_SESSIONS, the sandbox is still on (or the tmux socket
is otherwise blocked). Re-run the command with the sandbox disabled before
continuing — do NOT treat it as "no sessions."
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.
- 11d ago First seen · 99 lines · 18 tokens per session scan A 7e8c19736afc
teleport-tmux is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 1,111 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.