using-gpus

using-gpus is a skill for Claude Code from yale-som-hpc/claude-code-marketplace. It costs 67 tokens per session (2,395 once invoked), scanned A, original, Unlicense.

A guide for requesting and managing GPU jobs on the Yale SOM high-performance computing cluster, a shared system for running compute-heavy programs. It explains when code actually needs a GPU and when ordinary CPU work is enough.

In plain words
What is it for?
Use it when writing GPU batch scripts, running CUDA or GPU-based machine-learning code, or checking for idle GPU allocations on that cluster.
Why use it?
It helps avoid reserving scarce GPUs for downloads, data preparation, or other work that does not use them.

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 writing GPU batch scripts, running CUDA or GPU-based machine-learning code, or checking for idle GPU allocations on that cluster.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/using-gpus"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/using-gpus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,395 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.00067 $0.02395
Opus 5 $0.00034 $0.01197
Sonnet 5 $0.00013 $0.00479
Haiku 4.5 $0.00007 $0.00239

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

Security

Grade A, and why

using-gpus 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 9d 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/using-gpus/SKILL.md · 258 lines

How it starts

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

Using GPUs

Rule: hold a GPU only while GPU code is actively running. Do CPU preprocessing, downloads, tokenization, and web/API calls elsewhere.

GPUs are the scarcest resource on the cluster. An idle interactive GPU session — srun --pty bash left open while you go to lunch — is blocking another user's job right now. Cancel it. The H100 partition now has two 4-GPU nodes when healthy, but it remains the scarcest partition; treat it accordingly.

Account for every GPU-hour

Treat each requested GPU-hour as compute somebody else cannot use. The cluster has finite GPUs and H100s are scarce; there are no per-user GPU caps, so it is on you to cancel idle GPU jobs the instant you notice them — scancel JOBID — and never request more GPUs than your code uses.

Do you need a GPU?

Use a GPU for:

  • deep learning training
  • transformer/LLM inference
  • CUDA/PyTorch/JAX/TensorFlow code
  • RAPIDS/CuPy code that is explicitly GPU-backed

Do not use a GPU for:

  • Stata regressions
  • fixest, pyfixest, statsmodels, or ordinary CPU dataframe work
  • data cleaning, merging, reshaping, tokenization
  • downloading data or making network/API requests
  • bootstrap/Monte Carlo unless code is actually CUDA-backed

Request one GPU first

#!/bin/bash
#SBATCH --job-name=gpu-test
#SBATCH --partition=gpunormal
#SBATCH --gres=gpu:1
#SBATCH --time=01:00:00
#SBATCH --cpus-per-task=4
#SBATCH --mem=32G
#SBATCH --output=logs/%x_%j.out

set -euo pipefail

export OMP_NUM_THREADS=${SLURM_CPUS_PER_TASK:-1}
export MKL_NUM_THREADS=${SLURM_CPUS_PER_TASK:-1}
export OPENBLAS_NUM_THREADS=${SLURM_CPUS_PER_TASK:-1}

nvidia-smi
# Environment was created during setup with: uv sync --frozen
srun .venv/bin/python train.py

Only request multiple GPUs if the code explicitly uses multiple GPUs.

Use gpunormal by default. (Note: gpunormal is the cluster's general production queue on the GPU nodes, not a GPU-only partition — you get a GPU only because you asked with --gres=gpu:1. A job there without --gres runs CPU-only and consumes no GPU. See overview for the partition map.) Use h100 only when H100 performance or 80 GB VRAM specifically matters:

Read the full file on GitHub · 258 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. 9d ago First seen · 258 lines · 67 tokens per session scan A 69f480cddf6c

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…

Jeffallan/claude-skills · 71 tokens