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 ma-compbio-lab/SkillFoundry --skill nextflow-hello-workflowgit clone --depth 1 https://github.com/ma-compbio-lab/SkillFoundryWrote 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/ma-compbio-lab/skillfoundry/nextflow-hello-workflow)<a href="https://agentmods.dev/skills/ma-compbio-lab/skillfoundry/nextflow-hello-workflow"><img src="https://agentmods.dev/badge/skills/ma-compbio-lab/skillfoundry/nextflow-hello-workflow/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/ma-compbio-lab/skillfoundry/nextflow-hello-workflow"><img src="https://agentmods.dev/badge/skills/ma-compbio-lab/skillfoundry/nextflow-hello-workflow.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.00046 | $0.00845 |
| Opus 5 | $0.00023 | $0.00423 |
| Sonnet 5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
nextflow-hello-workflow 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Verify that the repository-local Nextflow runtime works and execute a tiny deterministic workflow end to end, including a Slurm executor path.
When to use
- You need a small, local Nextflow smoke test.
- You want a known-good example before adapting a larger workflow.
- You want to confirm that Nextflow can submit tiny jobs to the local Slurm cluster.
When not to use
- You need container orchestration or production pipeline packaging.
Inputs
examples/main.nf- Optional
--out-dir,--work-dir, and executor settings - For cluster runs:
--executor slurmplus an optional partition
Outputs
- Published greeting files in the chosen output directory
- JSON summary with the runtime version, produced files, and optional Slurm trace/accounting details
Requirements
- The repo-local toolchain at
slurm/envs/nextflow-tools - Local filesystem write access for the work and output directories
- For cluster verification:
sbatchandsacctaccess on the local Slurm cluster
Procedure
- Run
python3 skills/reproducible-workflows/nextflow-hello-workflow/scripts/run_nextflow_hello.py --out-dir scratch/nextflow-hello/resultsfor a local smoke path. - Run
python3 skills/reproducible-workflows/nextflow-hello-workflow/scripts/run_nextflow_hello.py --executor slurm --partition cpu --out-dir scratch/nextflow-hello-slurm/results --work-dir scratch/nextflow-hello-slurm/work --summary-out scratch/nextflow-hello-slurm/summary.jsonfor a cluster-backed smoke path. - Inspect the returned
fileslist and the output directory contents. - For Slurm runs, inspect
trace_rowsandslurm_jobsin the summary. - Reuse the pattern in
examples/main.nfwhen bootstrapping larger pipelines.
Validation
nextflow infosucceeds through the repo-local wrapper environment.nextflow runcompletes without errors.- Four greeting files are published to the output directory.
- For Slurm runs, the trace file contains native job IDs and
sacctreportsCOMPLETEDwithExitCode 0:0.
What ships with it
21 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.
- assets/hello_run_outputs/Bonjour.txt 15 B
- assets/hello_run_outputs/Ciao.txt 12 B
- assets/hello_run_outputs/Hello.txt 13 B
- assets/hello_run_outputs/Hola.txt 12 B
- assets/hello_run_summary.json 1.5 KB
- assets/hello_slurm_summary.json 4.1 KB
- assets/latest-results/Bonjour.txt 15 B
- assets/latest-results/Ciao.txt 12 B
- assets/latest-results/Hello.txt 13 B
- assets/latest-results/Hola.txt 12 B
- assets/latest-slurm-results/Bonjour.txt 15 B
- assets/latest-slurm-results/Ciao.txt 12 B
- assets/latest-slurm-results/Hello.txt 13 B
- assets/latest-slurm-results/Hola.txt 12 B
- assets/README.md 439 B
- examples/main.nf 399 B
- examples/README.md 345 B
- metadata.yaml 1.4 KB
- refs.md 325 B
- scripts/run_nextflow_hello.py 7.6 KB runs code
- tests/README.md 260 B
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 · 68 lines · 46 tokens per session scan A 0676a09dd283
nextflow-hello-workflow is a skill published in the GitHub repository ma-compbio-lab/SkillFoundry (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 845 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-09-03.
Other skills, from other repositories
arxiv-search
Skill "arxiv-search" from TaewoooPark/MagLab, covering category scoping, query families (3–6 per topic), version and doi resolution, tier classification and output contract.
revision-letter
Point-by-point peer-review response letter workflow for journal resubmission. Invokes RevisionLetterAgent to quote each reviewer comment verbatim, draft a response, and add a change-location marker. Outputs carry HUMAN REVIEW REQUIRED; no auto-send. A DOI or manuscript location is required for every factual response…
literature-search
Broad literature search for magnetism & spintronics — OpenAlex REST query strategy, query family generation, tier classification, and evidencematrix construction (§14.3·§14.7). Activated by the maglab lit search command and the research orchestration search-scout agent.
physics-oracle
Use when validating the dimensional, range, and conservation-law plausibility of magnetic physics quantities, or when performing deterministic physics formula calculations and unit conversions. Gilbert damping 0≤α≤1 check, M≤Ms, exchange length and domain wall width calculations, Oe↔A/m↔T·emu/cm³↔A/m·Jij meV↔K…
statistical-experimental-evaluation
Design and run statistical experiments that test the formal problem, proposed methods, theoretical predictions, baselines, and ablations.
batch-effect-correction
Use when correcting batch effects in merged bulk expression matrices with sample-level batch metadata while preserving biological group structure and generating before-and-after QC plots. NOT for: single-cell integration, raw FASTQ processing, differential expression without batch labels, or datasets without…