There have been a few other modules like this, that are post-processing of tool output, that could potentially be within the tools rather than the probably not discoverable

custom

My thoughts are that

custom

should generally not exist, and anything that's related to the output of a tool should be in the same folder as the tool.

Agreed with Mahesh. I think it's nice to collect custom modules that process the outputs of tools with the tools themselves, for discoverability. If we need a custom at all it should be reserved for really general things

That is my feeling too

Anything custom also needs to be checked if it can be implemented with an existing module. I saw one recently that was just an awk script.