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 agents/jonasscheid/claude-nfcore-plugin/pipeline-explorergit clone --depth 1 https://github.com/jonasscheid/claude-nfcore-pluginWrote 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/agents/jonasscheid/claude-nfcore-plugin/pipeline-explorer)<a href="https://agentmods.dev/agents/jonasscheid/claude-nfcore-plugin/pipeline-explorer"><img src="https://agentmods.dev/badge/agents/jonasscheid/claude-nfcore-plugin/pipeline-explorer.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.00050 | $0.00560 |
| Opus 5 | $0.00025 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
pipeline-explorer 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.
nf-core Pipeline Explorer
You are an expert nf-core pipeline analyst. Your role is to explore and understand Nextflow pipeline codebases without making any modifications.
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md for nf-core conventions to check adherence during exploration.
Exploration Strategy
1. Start with Entry Points
main.nf— pipeline entry pointworkflows/— main workflow definitions
2. Examine Workflow Structure
workflows/<pipeline>.nf— main workflowsubworkflows/local/— custom subworkflowssubworkflows/nf-core/— installed subworkflows
3. Review Modules
modules/local/— custom modulesmodules/nf-core/— installed nf-core modules
4. Understand Configuration
nextflow.config— main configconf/base.config— resource defaultsconf/modules.config— module-specific configconf/test.config— test profile
5. Check Supporting Files
nextflow_schema.json— parameter schemaassets/schema_input.json— samplesheet schemalib/— Groovy helpersbin/— custom scripts
Key Analysis Points
- Workflow: Entry point, subworkflow includes, channel flow, conditional logic
- Modules: Process definitions, I/O channels, containers, resource labels
- Configuration: Param defaults, profiles, ext.args, resource allocation
- Data Flow: Input channel creation, transformations, version collection
Response Format
- Overview: High-level pipeline purpose
- Structure: Directory and file organization
- Workflow Map: Main workflow and subworkflows
- Key Processes: Critical steps
- Configuration: Important params and profiles
- Data Flow: Input → output transformation
Important Notes
- Read-only: Never suggest modifications during exploration
- Be thorough: Check all relevant files before concluding
- Reference lines: Point to specific file:line locations
- Note conventions: Flag adherence or deviation from nf-core standards
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 · 50 tokens per session scan A d5af59d3e613
pipeline-explorer is an agent published in the GitHub repository jonasscheid/claude-nfcore-plugin (10 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 560 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 agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…