connecting-securely

connecting-securely is a skill for Claude Code from yale-som-hpc/claude-code-marketplace. It costs 80 tokens per session (1,280 once invoked), scanned D, original, Unlicense.

A set of instructions for connecting securely to the Yale SOM HPC cluster, a shared system for running larger computing jobs. It covers SSH keys, connection reuse, jump hosts, and tunnels for tools such as VS Code or Jupyter.

In plain words
What is it for?
Use it when logging into hpc.som.yale.edu, connecting to compute nodes, forwarding ports, setting up VS Code or Jupyter tunnels, using GitHub through the cluster, or troubleshooting SSH connections.
Why use it?
It helps you access the cluster without copying private keys onto it and helps keep connections working through network interruptions or multiple login steps.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it when logging into hpc.som.yale.edu, connecting to compute nodes, forwarding ports, setting up VS Code or Jupyter tunnels, using GitHub through the cluster, or troubleshooting SSH connections.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/connecting-securely"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/connecting-securely.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 1,280 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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.00080 $0.01280
Opus 5 $0.00040 $0.00640
Sonnet 5 $0.00016 $0.00256
Haiku 4.5 $0.00008 $0.00128

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

Security

Grade D, and why

connecting-securely 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 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

chmod 700 ~/.ssh

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

scp ~/.ssh/id_ed25519 hpc:~/.ssh/
plugins/hpc/skills/connecting-securely/SKILL.md · 141 lines

How it starts

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

Connecting Securely

Rule: use SSH keys and agent forwarding; never copy private keys onto the cluster.

Do not copy private keys

Bad:

scp ~/.ssh/id_ed25519 hpc:~/.ssh/

Good:

ssh-add -l
ssh hpc

If you need GitHub from the cluster, use gh auth login or carefully scoped SSH agent forwarding. Do not store your laptop private key on GPFS. If gh is not installed, see installing software.

Local SSH config

Example ~/.ssh/config on your laptop:

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

Host b??? c???
    User yournetid
    ProxyJump hpc
    HostName %h.cm.cluster

ServerAliveInterval keeps NAT/firewalls from silently dropping an idle session; ControlMaster/ControlPersist reuse one warm connection across repeated logins. To keep long agent work alive across laptop sleep or wifi drops, see staying connected.

Enable ForwardAgent yes only if you need it for Git or another SSH hop. Agent forwarding is convenient, but any process you run on the remote host can ask your agent to sign while the connection is active.

Now login works:

ssh hpc

Only connect to a compute node after Slurm has allocated it to you. Use the hostname printed inside your allocation, then tunnel to that node.

Permissions

chmod 700 ~/.ssh
chmod 600 ~/.ssh/config
chmod 600 ~/.ssh/authorized_keys 2>/dev/null || true
chmod 700 ~

This is a shared system. Keep private files private: do not make your home directory, .ssh, .env, tokens, or project credentials group/world-readable.

SSH agent checks

ssh-add -l
ssh -T [email protected]

Inside tmux or a long-running shell, SSH_AUTH_SOCK can go stale. The value is only a path to the forwarded agent socket created by your current SSH login; it is not the key itself. If GitHub auth worked yesterday and fails today, do not copy keys to the cluster. Start a fresh SSH login, restart the shell, or look into refreshing SSH_AUTH_SOCK so it points at a current working socket owned by you.

Read the full file on GitHub · 141 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.

  1. 11d ago First seen · 141 lines · 80 tokens per session scan D a46766d564b0

Subscribe to this mod's changes

connecting-securely is a skill published in the GitHub repository yale-som-hpc/claude-code-marketplace (5 stars, last pushed 2mo ago), licensed Unlicense. It adds 80 tokens to every session and 1,280 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens