model pass

The Aegisflow Model Pass is the passer for the single most expensive thing in your graph: the MODEL. One model input, one model output, nothing in between. Sounds pointless until you've rebuilt a modular workflow where the model needs to reach a sampler three groups away without anyone auto-wiring the wrong checkpoint into it.

Why it exists

This is one of the pack's "passer" family, and every passer has the same rationale. Because their inputs are optional, they don't trip the behavior where ComfyUI and some custom node packs try to "fix" open required inputs by auto-connecting whatever matching output is handy - which, with models especially, is a great way to silently sample with the wrong checkpoint. Passers also act as nameable targets for Use Everywhere / Anything Everywhere invisible-broadcast nodes: rename this node, target it from a sender, and the model you loaded elsewhere shows up here at runtime.

The practical shape of it: a modular graph loads the checkpoint once at the top, and every section that needs the model has a Model Pass sitting on its receptor. It's the socket that says "this module wants a MODEL here," plus a plug so the template doesn't error while you're still wiring it.

Inputs and outputs

• model (MODEL, optional) - passed through unchanged.
• Output: model (MODEL).

No input means a None output. Expected when a sender delivers at runtime; an error if you wire an empty passer into a KSampler.

Installing it

Standard for the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/aegis72/aegisflow_utility_nodes

Restart ComfyUI, or find "AegisFlow Utility Nodes" in ComfyUI Manager. No downloads - it's pure Python over ComfyUI's existing types.

Where people get burned

A model passer won't load, merge, or apply a LoRA - route those upstream and pass the finished MODEL. And remember the empty-socket rule: if nothing fills the input and no sender targets the node, downstream gets nothing. It's a mailbox for your model, not a model source.