Borrowing it
Nothing to install: this file belongs to Zayne-sprague/Dr-Claude-Code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Zayne-sprague/Dr-Claude-Code/main/.claude/skills/run-job/SKILL.mdgit 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/run-job)<a href="https://agentmods.dev/skills/zayne-sprague/dr-claude-code/run-job"><img src="https://agentmods.dev/badge/skills/zayne-sprague/dr-claude-code/run-job.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.1 | $0.00078 | $0.02810 |
| Opus 5 | $0.00039 | $0.01405 |
| Sonnet 5 | $0.00016 | $0.00562 |
| Haiku 4.5 | $0.00008 | $0.00281 |
Grade A, and why
run-job 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 7d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Job Skill
This is a RIGID workflow. Complete every phase in order. Do not skip steps.
Phase 0: Pre-flight Checks
Before writing a single line of script:
0.1 — Read benchmark reference (if applicable)
If this job runs evaluation or RL training on a known benchmark, check the reference index:
.claude/references/datasets_and_tasks/datasets_and_tasks_map.md
If the benchmark appears in the index, read its reference file before continuing. The reference file contains:
- Correct evaluation method (do NOT guess at scoring)
- Known pitfalls (wrong data_source names, off-by-one errors, etc.)
- Prompt format and few-shot count
- Setup checklist for eval / RL training
If the benchmark is NOT in the index and the job is non-trivial, invoke /raca:benchmark-reference to create a reference before proceeding.
0.2 — Read the cluster config
cat .raca/clusters.yaml
Identify the target cluster. Extract:
type(slurm / runpod / local)default_partition,default_account,scratch_pathgres_format(typed:gpu:h100:Nvs generic:gpu:N)modules,conda_envif set- GPU type and VRAM (look up in the GPU reference table below if needed)
0.3 — Verify connectivity
For SLURM clusters:
raca ssh <cluster> "echo 'SSH OK' && whoami && squeue -u \$USER | head -5"
For RunPod: confirm $RUNPOD_API_KEY is set.
For local: check nvidia-smi.
If connectivity fails, stop and resolve before continuing.
0.4 — Estimate memory and time
Before any non-trivial job, estimate whether the model fits on the target GPU.
For training/inference jobs, consider:
- Model parameters × dtype size × overhead multiplier
- Sequence length effects on KV cache / activations
GPU VRAM Reference:
| GPU | VRAM | Notes |
|---|---|---|
| H200 | 141 GB | Best for 70B+ |
| GH200 | 96 GB | Unified memory |
| H100 | 80 GB | Flagship datacenter |
| A100 | 80 GB | Common in academic clusters |
| L40S | 48 GB | Strong for inference |
| A6000 | 48 GB | Workstation GPU |
| RTX 4090 | 24 GB | Consumer; great for dev |
| RTX 3090 | 24 GB | Consumer; older |
| T4 | 16 GB | Budget cloud |
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.
- 7d ago First seen · 312 lines · 78 tokens per session scan A f88339a8ee6a
run-job is a skill published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 2,810 once invoked, about $0.0004 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…