Skip to content
Back to search

seawulf-claude-code

MarketplaceWorks with Claude CodeGitHub

Claude Code plugins for Stony Brook University's SeaWulf HPC cluster.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/khaihernlow--seawulf-claude-code/badge.svg)](/listings/khaihernlow--seawulf-claude-code)

HTML

<a href="/listings/khaihernlow--seawulf-claude-code"><img src="/api/listings/khaihernlow--seawulf-claude-code/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add khaihernlow/seawulf-claude-code
/plugin install seawulf@seawulf-claude-code

**Updating:** installed plugins don't update themselves. To get the latest version, run these in a terminal, then restart Claude Code:

claude plugin marketplace update seawulf-claude-code
claude plugin update seawulf@seawulf-claude-code

You need a SeaWulf account (your PI's project number and a ticket to RCI) and Duo on your phone. On Windows, you also need WSL. Claude walks you through the rest the first time.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines
  1. {
  2. "name": "seawulf-claude-code",
  3. "owner": {
  4. "name": "Khai Hern Low",
  5. "url": "https://github.com/khaihernlow"
  6. },
  7. "description": "Claude Code plugins for Stony Brook University's SeaWulf HPC cluster.",
  8. "plugins": [
  9. {
  10. "name": "seawulf",
  11. "source": "./",
  12. "description": "Work on Stony Brook University's SeaWulf and NVwulf HPC clusters from Claude Code."
  13. }
  14. ]
  15. }
README.md · README · 185 lines
  1. # seawulf-claude-code
  2. A Claude Code plugin that lets Claude work on **Stony Brook University's HPC clusters**: SeaWulf, plus
  3. NVwulf for large GPU jobs. You don't need to know HPC, and Claude doesn't need to be told how the cluster
  4. works. Install it and ask.
  5. - **Connects safely.** SeaWulf asks for Duo on *every* new ssh connection, and 10 unanswered pushes lock your account. Claude uses one session per approval and never retries blindly.
  6. - **Runs jobs well:** picks the right queue, writes Slurm scripts (CPU, GPU, arrays), waits sensibly, and works out why a job failed or is still waiting.
  7. - **Knows the GPUs:** SeaWulf's are A100s (its older K80, P100 and V100 nodes were retired in November 2026); NVwulf has H200 and RTX PRO 6000 Blackwell GPUs, with its own account and queues.
  8. - **Sets software up properly:** modules, conda/Python envs outside the purged scratch space, CUDA/PyTorch/vLLM, containers.
  9. - **Knows the rules:** login-node limits, quotas, the 45-day scratch purge, how to move data in and out.
  10. Built from SBU Research Computing's documentation and checked on the live cluster. Every fact lists its source
  11. and date, and a bundled script lets Claude re-check the cluster instead of trusting stale notes.
  12. ## Contents
  13. [Install](#install) · [Try it](#try-it) · [Ways to work](#ways-to-work) ·
  14. [For a whole lab](#for-a-whole-lab) · [What's inside](#whats-inside) · [Testing](#testing) ·
  15. [Contributing](#contributing) · [Status](#status)
  16. ## Install
  17. In Claude Code:
  18. ```
  19. /plugin marketplace add khaihernlow/seawulf-claude-code
  20. /plugin install seawulf@seawulf-claude-code
  21. ```
  22. **Updating:** installed plugins don't update themselves. To get the latest version, run these in a terminal, then
  23. restart Claude Code:
  24. ```
  25. claude plugin marketplace update seawulf-claude-code
  26. claude plugin update seawulf@seawulf-claude-code
  27. ```
  28. You need a SeaWulf account (your PI's project number and a ticket to RCI) and Duo on your phone. On Windows,
  29. you also need WSL. Claude walks you through the rest the first time.
  30. ## Try it
  31. - *"Check whether my SeaWulf jobs finished and show me the errors from any that failed."*
  32. - *"Set up a conda env with PyTorch on SeaWulf and run train.py on one A100 for 6 hours."*
  33. - *"My job says OUT_OF_MEMORY, what do I change?"*
  34. - *"Run this script over these 200 input files on the cluster, 20 at a time."*
  35. - *"Why has my GPU job been pending all day?"*
  36. ## Ways to work
  37. SeaWulf asks for Duo on every new ssh connection (SSH keys only remove the password step), so how Claude
  38. connects matters. There are four ways; pick what fits how you work. The skill's knowledge (queues, limits,
  39. envs, failures) applies to all of them.
  40. | | Claude runs on | Duo | Setup | Good when |
  41. | --- | --- | --- | --- | --- |
  42. | **One session from your laptop** | Your laptop | One push per session; commands then take ~2 s with no pushes | ssh config; WSL on Windows | Your code and tools live on your laptop and the cluster runs it |
  43. | **On the SBU VPN** | Your laptop | Approved once at VPN connect; plain ssh after that | VPN client | You're on the VPN anyway |
  44. | **Claude Code on SeaWulf** | The login node (`module load claude-code`) | One push per login | Sign in to Claude there once; install this plugin there too | You work only on the cluster |
  45. | **Open OnDemand shell** | Anywhere | One login in the browser | None | You can't set anything up; you paste commands back and forth |
  46. You always authenticate yourself, and Claude never sees or stores your password.
  47. ### One session from your laptop
  48. `scripts/preflight.sh` checks your setup without connecting. `scripts/sw` then holds one session open for every
  49. command, plus `put`/`get` for files. Real output from 2026-11-20 (NetID replaced):
  50. ```
  51. $ scripts/preflight.sh
  52. Checking ssh setup for 'seawulf'
  53. ok Host seawulf -> milan.seawulf.stonybrook.edu as jdoe
  54. ok ControlMaster on (your own login can be reused by the session)
  55. ok your own login is open (master connection)
  56. next 'sw start' opens the long-lived session (ONE Duo push: tell the user first)
  57. $ scripts/sw start
  58. Duo push sent to the user's phone; waiting up to 120 s for approval...
  59. session open
  60. $ scripts/sw run <<'EOF'
  61. sbatch --test-only templates/gpu-a100.sbatch
  62. EOF
  63. sbatch: Job 2443554 to start at 2026-11-24T14:36:57 using 8 processors on nodes a100-02 in partition a100
  64. ```
  65. ### Claude Code on SeaWulf
  66. RCI provides Claude Code as a module. Log in (`ssh seawulf`, one push), then:
  67. ```
  68. tmux # so Claude survives a dropped connection
  69. module load claude-code
  70. claude auth login # once; stored in your SeaWulf home
  71. claude # then, inside Claude Code, install this plugin with the two /plugin commands above
  72. ```
  73. Claude then runs on the shared login node: commands are local, but the login-node limits (3 CPUs, 15 GB per user)
  74. apply to Claude and everything it runs there. Heavy work still goes through Slurm, which the skill handles.
  75. Signing in on the cluster hasn't been tested yet; reports welcome.
  76. Details for all four: [connecting.md](skills/using-seawulf/references/connecting.md).
  77. ## For a whole lab
  78. To offer the plugin to everyone who opens a project, commit this to the project's `.claude/settings.json`:
  79. ```json
  80. {
  81. "extraKnownMarketplaces": {
  82. "seawulf-claude-code": {"source": {"source": "github", "repo": "khaihernlow/seawulf-claude-code"}}
  83. },
  84. "enabledPlugins": {"seawulf@seawulf-claude-code": true}
  85. }
  86. ```
  87. ## What's inside
  88. | Path | What |
  89. | --- | --- |
  90. | [`skills/using-seawulf/SKILL.md`](skills/using-seawulf/SKILL.md) | What Claude reads first: the cluster in brief, the safety rules, how to connect, where to look next |
  91. | [`references/connecting.md`](skills/using-seawulf/references/connecting.md) | Accounts, hosts, OnDemand, ssh config and keys, Duo and lockouts, Windows/WSL, troubleshooting |
  92. | [`references/slurm.md`](skills/using-seawulf/references/slurm.md) | SeaWulf queues and limits, shared vs whole-node, A100 GPUs, batch and interactive jobs, arrays, dependencies, monitoring, failure causes |
  93. | [`references/software.md`](skills/using-seawulf/references/software.md) | Modules, conda/pip placement, GPU Python, Singularity, Jupyter and OnDemand apps |
  94. | [`references/storage-and-data.md`](skills/using-seawulf/references/storage-and-data.md) | Home, scratch, project space, quotas, the purge, moving data |
  95. | [`references/nvwulf.md`](skills/using-seawulf/references/nvwulf.md) | NVwulf: H200 and Blackwell GPU queues, limits, modules, and the quota that blocks jobs |
  96. | [`references/getting-help.md`](skills/using-seawulf/references/getting-help.md) | When to contact RCI, and drafting tickets you send yourself |
  97. | [`references/verified-facts.md`](skills/using-seawulf/references/verified-facts.md) | Every fact with its source and date |
  98. | [`templates/`](skills/using-seawulf/templates/) | Shared-CPU, A100 and array job scripts, validated on the cluster |
  99. | [`scripts/preflight.sh`](skills/using-seawulf/scripts/preflight.sh) | Checks your local setup and says what's missing (no Duo) |
  100. | [`scripts/sw`](skills/using-seawulf/scripts/sw) | The one-session runner: `start`, `run`, `put`/`get` files, `stop` (macOS, Linux, WSL; forwards from Git Bash) |
  101. | [`scripts/cluster-facts.sh`](skills/using-seawulf/scripts/cluster-facts.sh) | Current queues, limits, down nodes, your accounts, quotas, modules and jobs |
  102. | [`evals/`](evals/) | Test cases for Claude's behaviour with the skill |
  103. | [`CHANGELOG.md`](CHANGELOG.md) | What changed in each release |
  104. ## Testing
  105. **Behaviour:** [`evals/`](evals/) has six cases, each run three times with and without the plugin and graded on
  106. what Claude actually did (`claude plugin eval . --allow-tools Write`, Claude Code 2.1.329). Pass rates on
  107. 2026-11-20, with / without the plugin:
  108. | Case | Claude Opus 5.5 | Claude Haiku 5.5 |
  109. | --- | --- | --- |
  110. | Checks jobs without a Duo push per command | 100% / 56% | 100% / 44% |
  111. | Keeps conda envs out of purged scratch | 100% / 50% | 83% / 0% |
  112. | Writes a correct A100 job script | 100% / 67% | 75% / 50% |
  113. | Diagnoses an OUT_OF_MEMORY job | 100% / 83% | 83% / 50% |
  114. | Refuses heavy work on the login node | 100% / 100% (since tightened) | 89% / 0% |
  115. | Picks a queue for a small job | 100% / 100% | 100% / 58% |
  116. Haiku's misses led to the "Numbers used most" table and the explicit conda lines now in `SKILL.md` and the GPU
  117. template.
  118. **Triggering:** [`evals/triggering/`](evals/triggering/) checks that the skill activates for SeaWulf requests and
  119. stays quiet for near-misses (Slurm on other clusters, a personal GPU, Duo for email, course registration). Claude
  120. runs with only the Skill tool, so nothing touches the cluster. Result: 20/20 correct (Claude Opus 5.5).
  121. Both kinds are real, billed model runs (about $3 on Opus 5.5, under $1 on Haiku 5.5, about $1 for
  122. triggering), and none of them connect to SeaWulf or send Duo pushes.
  123. ## Contributing
  124. Corrections are especially welcome. The cluster changes, and some parts are only tested from one setup.
  125. - Found a problem? Open an [issue](https://github.com/khaihernlow/seawulf-claude-code/issues/new/choose); there are forms for bugs and for outdated cluster facts.
  126. - Check a fact on the cluster (`scripts/cluster-facts.sh` helps), then update the reference **and** its row in `verified-facts.md` with the date and how you checked it.
  127. - Keep personal details (NetIDs, paths, Slurm accounts) out of the repo.
  128. - Keep `SKILL.md` short: details go in `references/`, one level deep.
  129. - Releases are automatic: bump `version` in `.claude-plugin/plugin.json` and add its section to `CHANGELOG.md`; a GitHub release with those notes follows.
  130. ## Status
  131. Checked on 2026-11-20 against SeaWulf's milan login node, from Windows 11 with WSL (Ubuntu 24.04), on one
  132. user's account; NVwulf checked the same day. Not yet tested from macOS or Linux, or on other accounts.
  133. Related work: [hpc-skills](https://gitee.com/ktwu/hpc-skills) (Tufts, Northwestern, KAUST, EPFL) and
  134. [Cirrus skills](https://skills.cirrus.ac.uk/) take the same approach for other clusters.
  135. Not affiliated with or endorsed by Stony Brook University or Research Computing & Informatics. Follow SBU's
  136. acceptable-use policies; you're responsible for what runs under your account. For help with the clusters
  137. themselves, see [RCI's documentation](https://rci.stonybrook.edu/hpc/docs).
  138. ## License
  139. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.