Overview
On this page you will learn what module nodes are in Trickest, how they work, and how they relate to other building blocks and the Library.What is a Module Node
A module node is a reusable subgraph of nodes (tools, scripts, and optionally other modules) that appears as a single node in a workflow. Inside the module, multiple nodes are wired together to form an end-to-end process or use case. From the outside, the module has a clear boundary: it exposes inputs and outputs like any other node, so you can connect it upstream and downstream without caring about the internal steps. Modules let you encapsulate complexity and reuse the same pipeline across many workflows.Why Modules Exist
Building a workflow from dozens of tools and scripts works but can become hard to read and reuse. Modules solve that by grouping a logical sequence of steps into one unit. You can take a subgraph you use often (e.g. subdomain enumeration plus filtering plus output formatting), turn it into a module, and drop it into any workflow. Modules also make it easier to share and standardize processes: the Library offers ready-made modules for common offensive security use cases, and you can build and reuse your own.How It Works
A module is defined by its internal graph: the nodes it contains and the connections between them. Some of those nodes’ inputs and outputs are exposed at the module boundary and become the module’s inputs and outputs. When you add a module to a workflow, you connect to those boundary inputs and outputs the same way you would with a tool or script. When the workflow runs, the platform executes the module’s subgraph; from your perspective it behaves as one step. Modules can contain any mix of tools, scripts, and nested modules.How It Relates
- Building blocks: Modules are one of the three node types (scripts, tools, modules). See Introduction.
- Scripts and tools: A module is a container for scripts and tools (and other modules). Scripts and tools are single nodes; a module is a subgraph that looks like a single node from the outside.
- Workflows: Modules run as nodes in a workflow. You design workflows by combining tools, scripts, and modules. See Workflows.
- Library: The Library includes modules you can add to your workflows. You can also create modules from your own workflows and reuse them.
Common Patterns
- Using a Library module to run a full use case (e.g. recon or content discovery) with a few inputs instead of building the graph from scratch
- Turning a repeated sequence of tools and scripts in a workflow into a module and reusing it in other workflows
- Chaining modules with tools and scripts: e.g. a module’s output feeding a tool, or a tool’s output feeding a module
- Keeping workflows readable by hiding detailed steps inside modules and working with high-level inputs and outputs