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 skills add SciMate-AI/HPC-Skills --skill hpc-spackgit clone --depth 1 https://github.com/SciMate-AI/HPC-SkillsWrote 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/scimate-ai/hpc-skills/hpc-spack)<a href="https://agentmods.dev/skills/scimate-ai/hpc-skills/hpc-spack"><img src="https://agentmods.dev/badge/skills/scimate-ai/hpc-skills/hpc-spack/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.
<a href="https://agentmods.dev/skills/scimate-ai/hpc-skills/hpc-spack"><img src="https://agentmods.dev/badge/skills/scimate-ai/hpc-skills/hpc-spack.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00767 |
| Opus 5 | $0.00030 | $0.00383 |
| Sonnet 5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
hpc-spack 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 12d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HPC Spack
Treat Spack as a stack manager, not just an install command. Decide the compiler, MPI, externals, concretization policy, and environment boundary before changing package-level variants.
Start
- Read
references/spec-and-variant-matrix.mdbefore writing or repairing a Spack spec. - Read
references/compilers-and-external-packages.mdwhen compiler registration,packages.yaml, or external software ownership is in scope. - Read
references/environments-and-concretization.mdwhen usingspack.yaml, lockfiles, unified concretization, or multi-package environments. - Read
references/compiler-and-mpi-matrix.mdwhen the stack depends on compiler or MPI families and their combinations. - Read
references/modules-buildcaches-and-binary-reuse.mdwhen integrating site modules, buildcaches, mirrors, or binary reuse. - Read
references/site-stack-and-reproducibility.mdwhen the goal is a durable site stack, reproducible environment, or cluster handoff. - Read
references/error-recovery.mdwhen concretization, install, compiler detection, external-package, or reuse behavior fails.
Work sequence
- Decide the stack boundary first:
- site-provided externals
- project-local Spack environment
- site-maintained Spack stack
- Register compilers and externals before solving the dependency graph.
- Write the minimal spec or environment that captures the intended compiler and MPI choices.
- Concretize and inspect the solved graph before launching a long install.
- Capture environment manifests, overrides, and reuse settings with the build record.
Guardrails
- Do not mix ad hoc package installs and environment-managed installs casually.
- Do not force many variants at once before the compiler and external package model is coherent.
- Do not treat concretization policy as an afterthought when several packages must coexist.
- Do not hide site-provided MPI, CUDA, or math libraries from Spack if the cluster expects them to be reused as externals.
What ships with it
14 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.
- agents/openai.yaml 253 B
- assets/templates/compilers-example.yaml 322 B
- assets/templates/packages-external-example.yaml 213 B
- assets/templates/spack-build-smoke-slurm.sh 596 B runs code
- assets/templates/spack-create-env-and-install.sh 431 B runs code
- assets/templates/spack-env-minimal.yaml 93 B
- references/compiler-and-mpi-matrix.md 885 B
- references/compilers-and-external-packages.md 1.2 KB
- references/environments-and-concretization.md 1.0 KB
- references/error-pattern-dictionary.md 1.3 KB
- references/error-recovery.md 1.1 KB
- references/modules-buildcaches-and-binary-reuse.md 895 B
- references/site-stack-and-reproducibility.md 916 B
- references/spec-and-variant-matrix.md 1.4 KB
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.
- 12d ago First seen · 69 lines · 60 tokens per session scan A 061105fda02d
hpc-spack is a skill published in the GitHub repository SciMate-AI/HPC-Skills (86 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 767 once invoked, about $0.0003 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-30.
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…