What is check-availability?

A tool that checks how busy the Duke computer science cluster is, including whether particular graphics processors (GPUs) are available.

Use it before submitting computing jobs to check overall GPU availability or the status of an a5000, a6000, rtxpro6000, v100, p100, rtx2080, or rtx5000 GPU.

It helps you avoid submitting a job to a crowded or fully occupied part of the cluster. You can see running jobs and, when requested, an estimated start time.

check-availability — Skill for Claude Code and Codex by TianchenGuan

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 TianchenGuan/duke-cs-cluster-skill --skill check-availability

Clone the repo

git clone --depth 1 https://github.com/TianchenGuan/duke-cs-cluster-skill

Made for: Claude Code, Codex.

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/tianchenguan/duke-cs-cluster-skill/check-availability/github.svg)](https://agentmods.dev/skills/tianchenguan/duke-cs-cluster-skill/check-availability)

Your own site

<a href="https://agentmods.dev/skills/tianchenguan/duke-cs-cluster-skill/check-availability"><img src="https://agentmods.dev/badge/skills/tianchenguan/duke-cs-cluster-skill/check-availability/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/tianchenguan/duke-cs-cluster-skill/check-availability"><img src="https://agentmods.dev/badge/skills/tianchenguan/duke-cs-cluster-skill/check-availability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,007 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.00086	$0.01007
Opus 5.5	$0.00034	$0.00403
Sonnet 5.5	$0.00017	$0.00201
Haiku 4.5	$0.00009	$0.00101

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

Security

Grade A, and why

check-availability 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.

check-availability/SKILL.md · 74 lines

How it starts

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

Check Duke CS Cluster Availability

When invoked, produce a nicely formatted summary of current cluster state to help the user decide where to submit their next job.

Behavior

If no GPU type was specified: give an overall snapshot.

Run bash ~/.claude/skills/duke-cluster/scripts/check_cluster_load.sh to get the one-liner summary.
Also run sinfo -p compsci-gpu -o '%G %D %t' to get per-GPU-type idle counts.
Format into a single table showing each GPU type, total count, idle count, and a qualitative label ("free", "busy", "full").

If a specific GPU type was specified: drill down on that type.

Run bash ~/.claude/skills/duke-cluster/scripts/check_gpu_contention.sh <type>.
Optionally run bash ~/.claude/skills/duke-cluster/scripts/estimate_wait.sh <type> 1 to get a Slurm start estimate for a single-GPU placeholder.
Format the output into three sections: summary line, table of currently-running jobs on those nodes (job ID, user, GPUs, elapsed, remaining), and the Slurm start estimate.

Output format

Use markdown tables. Keep the response scannable — a user running this before submitting a job wants the answer in 2 seconds, not a paragraph.

For the overall snapshot, target this shape:

GPU type	Idle / Total	Status
a5000	18 / 124	Mostly free
a6000	0 / 16	Full
rtx_pro_6000	0 / 20	Full
v100	3 / 5	Mostly free
p100	8 / 25	Free
rtx_2080	12 / 22	Free
rtx_5000	2 / 5	Mixed

Add a one-sentence verdict underneath. Examples: "A5000 pool is healthy — submit and expect to start in seconds." / "A6000 and RTX Pro 6000 are fully allocated — consider A5000 or V100 instead."

For a specific GPU type, target:

A6000 (fitz-[05-08]) — 0 of 16 GPUs idle, 4 users running jobs.

Job ID User CPUs GPUs Elapsed Remaining Name

1234567 alice 32 gpu:a6000:4 2h 34m 5h 26m finetune

...

Slurm's start estimate for a new 1x A6000 job: 2026-04-13T18:23:00 (about 4 hours from now).

Verdict: long wait expected. If your job is less than 48GB VRAM, consider A5000 instead.

Job ID	User	CPUs	GPUs	Elapsed	Remaining	Name
1234567	alice	32	gpu:a6000:4	2h 34m	5h 26m	finetune
...

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

2mo ago First seen · 74 lines · 86 tokens per session scan A 17ecd5ee9151

Subscribe to this mod's changes

check-availability is a skill published in the GitHub repository TianchenGuan/duke-cs-cluster-skill (6 stars, last pushed 6mo ago), licensed MIT. It adds 86 tokens to every session and 1,007 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.

Scientific

check-availability next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
check-availabilityTianchenGuan/duke-cs-cluster-skill	Skill	6	6mo ago	MIT	A	86	Claude Code, Codex
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