A guide to Slurm, a system that schedules computing jobs on shared clusters. It covers reusable commands and patterns for submitting, monitoring, and debugging work without assuming one site's local settings.

Use it for CPU or GPU batch scripts, interactive jobs, job arrays, dependency pipelines, monitoring, accounting, and troubleshooting pending or failed jobs.

It helps turn ad hoc commands or shell loops into repeatable jobs while avoiding invented cluster-specific accounts, queues, paths, or software names. Local values are marked for verification when unknown.

slurm-core — Skill for Claude Code by HCAI-Lab-GT/gt-hive

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 HCAI-Lab-GT/gt-hive --skill slurm-core

Clone the repo

git clone --depth 1 https://github.com/HCAI-Lab-GT/gt-hive

Made for: Claude Code.

Or install gt-hive-pace, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hcai-lab-gt/gt-hive/slurm-core/github.svg)](https://agentmods.dev/skills/hcai-lab-gt/gt-hive/slurm-core)

Your own site

<a href="https://agentmods.dev/skills/hcai-lab-gt/gt-hive/slurm-core"><img src="https://agentmods.dev/badge/skills/hcai-lab-gt/gt-hive/slurm-core/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hcai-lab-gt/gt-hive/slurm-core"><img src="https://agentmods.dev/badge/skills/hcai-lab-gt/gt-hive/slurm-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,559 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.

Model	Per session	Once invoked
Fable 5.1	$0.00071	$0.02559
Opus 5.5	$0.00028	$0.01024
Sonnet 5.5	$0.00014	$0.00512
Haiku 4.5	$0.00007	$0.00256

Measured 2mo ago against content hash bbae135ad870, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

slurm-core 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 2mo 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.

claude/skills/slurm-core/SKILL.md · 222 lines

How it starts

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

Slurm Core

This skill teaches a terminal AI assistant how to help with portable Slurm workflows without inventing site-local facts.

What this skill is for

Use this skill when the user needs help with:

CPU, Python, or GPU batch scripts
sbatch, srun, or salloc
job arrays
dependency pipelines
monitoring and debugging
accounting and exit-code interpretation
converting ad hoc shell loops into repeatable Slurm workflows

Before drafting anything, build context:

Identify the task type (job submission, resource selection, monitoring, troubleshooting).
Identify the workload profile (CPU, GPU, MPI, array, interactive debugging, I/O-heavy).
State assumptions explicitly and continue unless cluster policy or data handling forces a clarifying question.

What this skill must not guess

Do not invent any of the following:

cluster-specific --account
--partition
--qos
module names
filesystem paths
conda environment names
site policy
GPU type names that the cluster may not actually provide

If a value is unknown, mark it VERIFY_ON_SITE and explain what local doc or command should confirm it. The literal string VERIFY_ON_SITE is the convention readers grep for: it tells humans "the AI refused to invent this — fill it in yourself before submitting." Use it everywhere a site-local fact would otherwise be hallucinated (for example --account=VERIFY_ON_SITE, module load VERIFY_ON_SITE).

For reader-supplied values that are not site-secret (a job name, a script path), use angle-bracket placeholders like <job_name> or <script.py>.

Operating principles

Prefer long-form Slurm directives (--cpus-per-task=4, not -c 4) so scripts read as teaching material.
Prefer explicit resource requests to implicit defaults.
Keep explanations beginner-friendly but technically correct.
Separate portable Slurm ideas from site-local details. Portable goes in this skill; site-local goes in the overlay.
When the user is debugging, start from evidence rather than speculation.

Read the full file on GitHub · 222 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 222 lines · 71 tokens per session scan A bbae135ad870

Subscribe to this mod's changes

slurm-core is a skill published in the GitHub repository HCAI-Lab-GT/gt-hive (6 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 2,559 once invoked, about $0.0003 per session on Opus 5.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.

DevOps and cloud Scientific

slurm-core next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slurm-coreHCAI-Lab-GT/gt-hive	Skill	6	3mo ago	MIT	A	71	Claude Code
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	2d ago	Apache-2.0	A	123	Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skills	Skill	56k	4d ago	MIT	A	83	Claude Code
matlabK-Dense-AI/scientific-agent-skills	Skill	56k	4d ago	MIT	A	44	Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skills	Skill	56k	4d ago	MIT	A	71	Claude Code, Codex
research-engineerdavila7/claude-code-templates	Skill	33k	yesterday	MIT	A	43	Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmed	Skill	5.8k	yesterday	Apache-2.0	A	205	Claude Code