What is staying-connected?

Guidance for keeping work running on Yale SOM's shared computing cluster when an SSH connection drops. SSH is the remote terminal connection used to access the cluster, while tmux and zmx keep sessions alive.

Running Claude Code or long commands on the cluster, choosing between running the agent on the cluster or laptop, and maintaining durable remote sessions.

It prevents laptop sleep, Wi-Fi loss, or a closed terminal from stopping work or losing the remote shell's working directory and settings.

staying-connected — Skill for Claude Code by yale-som-hpc

Install

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.

Any agent

npx skills add yale-som-hpc/claude-code-marketplace --skill staying-connected

Clone the repo

git clone --depth 1 https://github.com/yale-som-hpc/claude-code-marketplace

Made for: Claude Code.

Or install hpc, the plugin that ships this one along with the rest of its 23 skills, 3 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/staying-connected/github.svg)](https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/staying-connected)

Your own site

<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/staying-connected"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/staying-connected/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/staying-connected"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/staying-connected.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,181 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00080	$0.02181
Opus 5.5	$0.00032	$0.00872
Sonnet 5.5	$0.00016	$0.00436
Haiku 4.5	$0.00008	$0.00218

Measured 2mo ago against content hash 4ef69295f877, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

staying-connected 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 2mo 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.

plugins/hpc/skills/staying-connected/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Staying Connected

Rule: a dropped laptop connection should never kill cluster work. Pick a model up front, make the session durable, and keep the agent's own footprint off the login node.

There are two ways to run Claude Code against the cluster. They fail differently, so they need different tools. Decide which one you are in before anything else.

Model	Claude Code runs on	What breaks on a drop	Fix
A	the cluster login node (you SSH in, then start Claude there)	the agent process is killed when your SSH dies	session persistence on the login node (tmux)
B	your laptop, driving the cluster over SSH	each `ssh hpc <cmd>` is a fresh shell that forgets cwd/modules/env	a persistent remote shell (zmx)

Cluster facts agents should know

Current as of 2026-06-05. Verify with command -v on the login node before recommending a tool.

tmux (3.2a) is installed system-wide on the login node. It is the default persistence tool.
mosh, mosh-server, screen, autossh, and Eternal Terminal (et) are not installed on the cluster. mosh and ET need a server-side binary, so they are unavailable until SOM IT installs them — see resilience ladder.
zellij and zmx are not system-wide; they only work if a user installed them under ~/.local/bin.
hpc.som.yale.edu currently resolves to a single login node (hpc-ln02). There is a second login node on the internal network, but the public name points at one host today, so a tmux session is reliably where you left it. This can change — see the reattach gotcha.

Baseline: SSH config (do this regardless of model)

On your laptop, ~/.ssh/config. This keeps idle links from being silently dropped and reuses one connection for the agent's many ssh calls:

Host hpc
    HostName hpc.som.yale.edu
    User yournetid
    ServerAliveInterval 60
    ServerAliveCountMax 3
    ControlMaster auto
    ControlPath ~/.ssh/cm-%r@%h:%p
    ControlPersist 10m

Read the full file on GitHub · 135 lines

Changes

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.

2mo ago First seen · 135 lines · 80 tokens per session scan A 4ef69295f877

Subscribe to this mod's changes

staying-connected is a skill published in the GitHub repository yale-som-hpc/claude-code-marketplace (5 stars, last pushed 3mo ago), licensed Unlicense. It adds 80 tokens to every session and 2,181 once invoked, about $0.0003 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-31.

Cloud DevOps and cloud

staying-connected next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
staying-connectedyale-som-hpc/claude-code-marketplace	Skill	5	3mo ago	Unlicense	A	80	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
gke-reliabilitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	85	Claude Code, Codex
gke-workload-securitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	171	Claude Code, Codex
cloud-architectJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	71	Claude Code
nemo-automodel-launcher-configNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code