Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jonasscheid/claude-nfcore-plugin/plugin install nf-coreWrote 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/jonasscheid/claude-nfcore-plugin/nf-test)<a href="https://agentmods.dev/skills/jonasscheid/claude-nfcore-plugin/nf-test"><img src="https://agentmods.dev/badge/skills/jonasscheid/claude-nfcore-plugin/nf-test.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.00062 | $0.01874 |
| Opus 5 | $0.00031 | $0.00937 |
| Sonnet 5 | $0.00012 | $0.00375 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
nf-test 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 6d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nf-test Testing
Run and manage tests using nf-test for Nextflow pipelines and modules.
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md for nf-core conventions and package manager setup.
Read ${CLAUDE_PLUGIN_ROOT}/shared/test-patterns.md for test templates and patterns.
Quick Commands
Replace <cmd> with the configured package manager prefix (see Setup in conventions.md).
<cmd> nf-test test # Run all tests
<cmd> nf-test test tests/modules/fastqc/ # Specific path
<cmd> nf-test test --profile +docker # Add container profile (+ ADDS, no + REPLACES)
<cmd> nf-test test --tag "modules" # Filter by tag
<cmd> nf-test test --update-snapshot # Update snapshots
<cmd> nf-test test --verbose # Verbose output
<cmd> nf-test list # List available tests
Process Tests
nextflow_process {
name "Test Process FASTQC"
script "../main.nf"
process "FASTQC"
tag "modules"
tag "fastqc"
test("Single-end reads") {
when {
process {
"""
input[0] = [
[ id:'test', single_end:true ],
file(params.test_data['sarscov2']['illumina']['test_1_fastq_gz'], checkIfExists: true)
]
"""
}
}
then {
assert process.success
assert snapshot(process.out).match()
}
}
test("Stub run") {
options "-stub"
when {
process {
"""
input[0] = [ [ id:'test' ], file('dummy.fastq.gz') ]
"""
}
}
then {
assert process.success
assert snapshot(process.out).match()
}
}
}
Pipeline-Level Tests
Pipeline tests use nextflow_pipeline (NOT nextflow_workflow) and load params via profiles.
Params are NEVER defined inline — they go in conf/test_XYZ.config.
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.
- 6d ago First seen · 270 lines · 62 tokens per session scan A dc12d7568708
nf-test is a skill published in the GitHub repository jonasscheid/claude-nfcore-plugin (10 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,874 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-31.
Other skills, from other repositories
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.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.