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 agentmods add skills/zayne-sprague/dr-claude-code/setup-clusternpx skills add Zayne-sprague/Dr-Claude-Code --skill setup-clustergit clone --depth 1 https://github.com/Zayne-sprague/Dr-Claude-CodeWrote 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/zayne-sprague/dr-claude-code/setup-cluster)<a href="https://agentmods.dev/skills/zayne-sprague/dr-claude-code/setup-cluster"><img src="https://agentmods.dev/badge/skills/zayne-sprague/dr-claude-code/setup-cluster.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.02994 |
| Opus 5 | $0.00036 | $0.01497 |
| Sonnet 5 | $0.00014 | $0.00599 |
| Haiku 4.5 | $0.00007 | $0.00299 |
Grade A, and why
setup-cluster scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bearer $RUNPOD_API_KEY" \ How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cluster Setup Skill
This is a RIGID workflow. Follow every step. Do not skip phases. Ask before proceeding at each gate.
GPU Memory Reference Table
Use this when estimating GPU requirements:
| GPU | VRAM | Notes |
|---|---|---|
| H200 | 141 GB | Best for 70B+ models |
| H100 SXM | 80 GB | Flagship datacenter GPU |
| H100 PCIe | 80 GB | Slightly lower bandwidth than SXM |
| A100 SXM | 80 GB | Common in academic clusters |
| A100 PCIe | 80 GB | Common in academic clusters |
| GH200 | 96 GB | Grace Hopper — CPU+GPU unified mem |
| L40S | 48 GB | Strong for inference |
| A6000 | 48 GB | Workstation GPU |
| V100 | 32 GB | Older; common in legacy clusters |
| RTX 4090 | 24 GB | Consumer; great for local dev |
| RTX 3090 | 24 GB | Consumer; older |
| RTX 4080 | 16 GB | Consumer mid-range |
| T4 | 16 GB | Common in cloud / budget clusters |
| RTX 3080 | 10 GB | Consumer entry |
| RTX 4070 | 12 GB | Consumer mid-range |
Phase 0: Identify Cluster Type
Ask the user:
"What type of cluster are you setting up?
- SLURM (university HPC, national lab, etc.)
- RunPod (cloud GPU rental)
- Local machine (workstation or server you control directly)"
Route to the appropriate phase based on their answer.
Phase 1a: SLURM Cluster Setup
Step 1.1 — Gather connection info
FIRST: Check ~/.ssh/config for existing aliases.
cat ~/.ssh/config 2>/dev/null
If the user's cluster name already appears as a Host entry in their SSH config, you already have the hostname, user, port, and key. Tell the user: "I found <name> in your SSH config — using hostname <hostname>, user <user>." Use those values directly.
Hostname validation: A valid SSH hostname looks like:
- A FQDN:
login.torch.hpc.nyu.edu,frontera.tacc.utexas.edu - An IP:
192.168.1.100 - An SSH config alias: a short name that appears as
Host <name>in~/.ssh/config
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.
- 3d ago First seen · 333 lines · 71 tokens per session scan A 65b8b9f1717c
setup-cluster is a skill published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 2,994 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
rule
Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.