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.
npx skills add yale-som-hpc/claude-code-marketplace --skill overviewgit clone --depth 1 https://github.com/yale-som-hpc/claude-code-marketplaceWrote 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.
[](https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/overview)<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/overview"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/overview/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.
<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/overview"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00069 | $0.02997 |
| Opus 5 | $0.00034 | $0.01499 |
| Sonnet 5 | $0.00014 | $0.00599 |
| Haiku 4.5 | $0.00007 | $0.00300 |
Grade A, and why
overview 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Use the cluster as a shared research instrument. Your job is not just to make code run; it is to request the right resources, avoid repeat work, and leave scarce resources available when you are not using them.
Mental model
- Login nodes are for editing, Git, modules, small installs, and submitting jobs.
- Compute nodes are for Python/R/Stata analysis, simulations, model training, and notebooks.
- Slurm allocates CPUs, memory, GPUs, and time.
- GPFS is shared storage. It likes large files; it dislikes millions of tiny files.
- Modules provide cluster-managed software: Python, R, Git, CUDA, Stata, MATLAB, etc.
- Project space under
/gpfs/project/is for shared research projects. - Scratch under
/gpfs/scratch60/is temporary working space. Treat it as a staging area, not an archive; remove large intermediates when a project or run is done.
Cluster facts agents should know
Current as of 2026-06-09. Verify live details with sinfo -s (and sinfo -a for restricted partitions) when generating production instructions.
- Scheduler: Slurm. Module system: Lmod (Spack-built; users run
module load, neverspack). - Partitions (six; use
sinfo -ato see all):default_queue— the Slurm default, but a short, small one: 1h default / 4h max, only 6 nodes (b001–002 + c018–021). Good for quick test jobs; not the place for long or large work.cpunormal— CPU-only production queue, no time limit (c018–021).gpunormal— the general production queue on the GPU-equipped nodes, no time limit, and by far the most capacity (sinfo -sfor live node/core counts). Despite the name it is not GPU-only: CPU jobs run here too (request a GPU with--gres=gpu:…, omit it for CPU work). In fact most of the cluster's CPU cores live on these nodes, so large CPU work realistically runs here — but mind your CPU/RAM reservation so you don't strand idle GPUs (see managing jobs). Holds RTX 8000 and A100 nodes, several GPUs per node (sinfo -N -p gpunormal -o "%N %G"for the live map).h100— 4 H100s per node, two nodes / 8 H100s when healthy. The scarcest GPU resource.build— A40 build nodes (b001–002).mbacourse— access-restricted course partition (you'll see it insinfo -abut likely cannot submit to it). It shares nodes c001–008 and c018–021 with the queues above.
cpunormal/gpunormalare the matched "normal" production tier (no time limit);default_queueis just a 4h-capped default on a few nodes. For real, long, or large work prefercpunormal/gpunormal.- The partitions overlap on shared hardware, so the cluster can look idle yet your job still pends. The CPU nodes c018–021 are claimed by
default_queue,cpunormal, andmbacourse; when a higher-priority partition (e.g.mbacourse) holds them, adefault_queuejob pends with reason "Nodes required for job are DOWN, DRAINED or reserved for jobs in higher priority partitions" even whilegpunormal's c001–017 sit mostly idle. Always read the pending reason (squeue --me -o "%T %r") and check idle cores per partition (sinfo -o "%R %C") rather than assuming "the cluster is full." - The
h100partition is still the scarcest GPU resource. Check live state before targeting it; drained or invalid nodes are unavailable even if they appear in the partition. /gpfs/project/for shared team projects (request via [email protected])./gpfs/scratch60/$USER/for scratch (clean it). Each compute node also has local/tmp(~20 GB NVMe),/local(~700 GB NVMe), and/dev/shm(RAM-backed, ~half the node's memory) — all per-node and not auto-cleaned by Slurm. See using the filesystem.$HOMEis/home/$USER, same as/gpfs/home/$USER.KillWait=30: after finalSIGTERM, jobs have ~30 seconds beforeSIGKILL. Too short to rely on for checkpointing.
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.
- 10d ago First seen · 152 lines · 69 tokens per session scan A 908b6492fa6f
overview is a skill published in the GitHub repository yale-som-hpc/claude-code-marketplace (5 stars, last pushed 2mo ago), licensed Unlicense. It adds 69 tokens to every session and 2,997 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…