hpc-connect

hpc-connect is a command for Claude Code from yale-som-hpc/claude-code-marketplace. It costs 15 tokens per session (251 once invoked), scanned A, original, Unlicense.

A connection setup command for the Yale SOM high-performance computing cluster that keeps work available after laptop sleep or unreliable Wi-Fi. It uses secure shell connections and persistent terminal sessions.

In plain words
What is it for?
Use it to configure SSH keep-alive settings, choose between working from the login node or laptop, start tmux or another persistent session, and reconnect later.
Why use it?
It prevents a dropped connection from ending your working session while reminding you that heavy computation must run through the cluster’s job scheduler.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the hpc plugin — 23 skills, 3 commands shipped together

Good fit Use it to configure SSH keep-alive settings, choose between working from the login node or laptop, start tmux or another persistent session, and reconnect later.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yale-som-hpc/claude-code-marketplace/hpc-connect
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.

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.

agentmods badge for hpc-connect

README.md
[![agentmods](https://agentmods.dev/badge/commands/yale-som-hpc/claude-code-marketplace/hpc-connect/github.svg)](https://agentmods.dev/commands/yale-som-hpc/claude-code-marketplace/hpc-connect)
Your own site
<a href="https://agentmods.dev/commands/yale-som-hpc/claude-code-marketplace/hpc-connect"><img src="https://agentmods.dev/badge/commands/yale-som-hpc/claude-code-marketplace/hpc-connect/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.

agentmods 80×15 button for hpc-connect

Your own site · 80×15
<a href="https://agentmods.dev/commands/yale-som-hpc/claude-code-marketplace/hpc-connect"><img src="https://agentmods.dev/badge/commands/yale-som-hpc/claude-code-marketplace/hpc-connect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 251 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00251
Opus 5 $0.00008 $0.00125
Sonnet 5 $0.00003 $0.00050
Haiku 4.5 $0.00002 $0.00025

Measured 10d ago against content hash 0bad5ef0e8d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

hpc-connect 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 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.

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/commands/hpc-connect.md · 16 lines

What it actually says

Help me connect to the Yale SOM HPC cluster so my work survives a dropped laptop connection.

Follow the staying-connected and connecting-securely skills. Steps:

  1. Ask whether I want to run Claude Code on the login node (Model A) or on my laptop driving the cluster (Model B) — explain the difference in one sentence each if I'm unsure.
  2. Check my ~/.ssh/config and add the recommended baseline (ServerAliveInterval, ControlMaster) if missing.
  3. For Model A: set me up to run inside tmux and show me the detach/reattach commands.
  4. For Model B: set up a persistent zmx SSH session if zmx is installed, otherwise show me the self-contained ssh hpc '...' pattern.
  5. Remind me of the footprint rule: a persistent session is a shell, not a compute host — heavy work goes through srun/sbatch.

Verify which tools are actually installed (command -v tmux zellij zmx autossh) before recommending one.

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.

  1. 10d ago First seen · 16 lines · 15 tokens per session scan A 0bad5ef0e8d7

Subscribe to this mod's changes

hpc-connect is a command published in the GitHub repository yale-som-hpc/claude-code-marketplace (5 stars, last pushed 2mo ago), licensed Unlicense. It adds 15 tokens to every session and 251 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-31.