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/nextflow-io/agent-skills/create-workflownpx skills add nextflow-io/agent-skills --skill create-workflowgit clone --depth 1 https://github.com/nextflow-io/agent-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/nextflow-io/agent-skills/create-workflow)<a href="https://agentmods.dev/skills/nextflow-io/agent-skills/create-workflow"><img src="https://agentmods.dev/badge/skills/nextflow-io/agent-skills/create-workflow.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.00078 | $0.01451 |
| Opus 5 | $0.00039 | $0.00726 |
| Sonnet 5 | $0.00016 | $0.00290 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade A, and why
create-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 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.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nextflow Workflow Writer
Create complete Nextflow workflows by composing validated modules from the Nextflow Registry.
Modules are published under namespaces (e.g. nf-core/fastqc), and these skills compose modules from any of them.
Requires Nextflow 26.04 or later (for the nextflow module commands used during validation).
NEVER write a wrapper workflow just to run/test a single module.
❌ WRONG - Writing a workflow to run one module:
// DO NOT DO THIS - not even when a module run fails!
include { FASTQC } from 'nf-core/fastqc'
workflow { FASTQC(Channel.fromPath('data/*.fq.gz')) }
✅ CORRECT - Use the run-module skill:
Skill(skill="run-module")
The run-module skill:
- Uses
nextflow module search/viewto discover and get proper inputs/parameters - Runs modules directly via
nextflow module run <namespace>/<module> - No wrapper workflow needed
⚠️ When a module run fails due to missing args:
- DO NOT write a wrapper workflow as a "fix"
- Instead: run
nextflow module view <module>to get correct parameters - Fix the command-line arguments and re-run directly
Only write a workflow in Step 4 when composing multiple validated modules together.
4-Step Workflow Creation Process
ALWAYS follow this structured process when creating a new workflow:
Step 1: Identify Modules and Propose Plan
- Use
nextflow module search <term>to find Registry modules for each processing step - Use
nextflow module view <name>to understand inputs/outputs of each module - Present a plan to the user with:
- List of identified modules
- Processing sequence (which module runs first, second, etc.)
- Data flow between modules (outputs → inputs)
STOP and wait for user approval before proceeding.
Step 2: User Agreement
- Wait for user to review and approve the proposed plan
- Address any questions or modifications requested
- Only proceed when user explicitly agrees
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 · 161 lines · 78 tokens per session scan A cb038d5bc1c2
create-workflow is a skill published in the GitHub repository nextflow-io/agent-skills (21 stars, last pushed 28d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,451 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-30.
Other skills, from other repositories
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…
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…
extracting-pii-entities
Detect PHI/PII spans in clinical text with OpenMed's extractpii without altering the text. Use when the user wants to find names, dates, MRNs, phone numbers, addresses, SSNs, or other identifiers and get their offsets and labels (not redact them), inspect what would be removed before de-identifying, route spans to a…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
tooluniverse-clinical-guidelines
Search and retrieve clinical practice guidelines from 12+ authoritative sources — NICE, WHO, NCCN, AHA, ADA, SIGN, USPSTF, IDSA, NIH consensus, ESMO/ESC/EASL European societies, and US specialty associations. Use for evidence-graded treatment recommendations, dosing protocols, screening guidance, and…
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…