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/lacerbi/dotclaude/hpcnpx skills add lacerbi/dotclaude --skill hpcgit clone --depth 1 https://github.com/lacerbi/dotclaudeWrote 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/lacerbi/dotclaude/hpc)<a href="https://agentmods.dev/skills/lacerbi/dotclaude/hpc"><img src="https://agentmods.dev/badge/skills/lacerbi/dotclaude/hpc.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.00031 | $0.00803 |
| Opus 5 | $0.00015 | $0.00402 |
| Sonnet 5 | $0.00006 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
hpc 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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hpc — launch work on the HPC cluster
You run the hpc launcher yourself to put the user's work on the cluster. That is
the point of the tool — do not hand commands to the user to run, unless asked.
1. Find the launcher
-
Look for its path in the user's global
~/.claude/CLAUDE.md, under an## hpc-launcher locationheading. -
If it isn't there, discover it: run
command -v hpcwith the Bash tool (Git Bash) and take the directory of that path. If that fails, ask the user where thehpc-launcherfolder is. -
Record it so later calls skip discovery — append to
~/.claude/CLAUDE.md:## hpc-launcher location The `hpc` launcher (for the /hpc skill) is at: `<path>`Keep
<path>~-relative when it's under home — that file is public, so a machine-specific absolute won't travel (and needlessly shows the username).
2. Read the launcher's own docs
<path>/README.md— what it does, setup, every command. Always.<path>/clusters/<HPC_CLUSTER>.md— facts for the cluster this repo targets (HPC_CLUSTERin.hpc.env;hpc clusterslists them). Read it when running or configuring a job — partitions, filesystem, gotchas (e.g. Roihu's split login hosts + 24 h SSH cert).<path>/AGENTS.md,DESIGN.md,TODO.md— only when you need rationale, limitations, or current status.
Read the live files. Do not rely on remembered defaults (partitions, modules,
torch module/wheel, walltimes) — they live in the cluster's clusters/<name>.env
profile and hpc-env.example, not in your memory.
3. Run it yourself
hpcis bash; use the Bash tool (Git Bash / MSYS), not PowerShell.- Execute the commands directly —
hpc run,hpc test,hpc status,hpc logs,hpc collect,hpc upload,hpc wait,hpc init, etc. Don't delegate them to the user. (For unattended/scripted use,hpc waitblocks until a job is done and exits its rc, andhpc status --json/hpc logs --onceare non-interactive — see the README.) - Auth: the user's ssh-agent holds the cluster key. If an
hpccall fails on SSH auth, ask the user to load it once (ssh-addtheir key), then keep running the commands yourself. - A project needs a
.hpc.env(runhpc init) beforehpc run/hpc test. hpc cancelrefuses to kill a RUNNING job unless you pass--force. If you were only cancelling because the job was stuck in the queue, the refusal means it has now started — so the reason to cancel is gone; let it run. Only--forceif you'd kill it regardless of queue state (bugged code, wrong config, superseded run).
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.
- 5d ago First seen · 61 lines · 31 tokens per session scan A 4258b8a03ad9
hpc is a skill published in the GitHub repository lacerbi/dotclaude (2 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 803 once invoked, about $0.0002 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
clinical-case-report
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…
kami-deck
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.
imaging-data-commons
Query and download public cancer imaging data from NCI Imaging Data Commons. Invoke for any question about IDC collections, cancer imaging datasets, DICOM data access, radiology (CT, MR, PET) or pathology AI training sets, metadata queries, visualization, or license checks — even when the user doesn't explicitly…
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
pkpd-modeling
Pharmacokinetic and pharmacodynamic modelling and simulation - non-compartmental analysis, compartmental and population PK, PK/PD and exposure-response, TMDD, PBPK orientation, bioequivalence, allometric scaling and first-in-human dose, drug interaction prediction, and Bayesian therapeutic drug monitoring. Use when…
biopython
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use…