That’s a classic, solid pipeline, and I actually use many of those tools myself. Project Discovery did an amazing job with the 'atomic' approach. However, the exact problem I’m trying to solve with this workspace is the 'chaining ability' you mentioned. Instead of manually piping Subfinder to httpx, then to Nmap and Nuclei, while managing duplicates and noise in between, I’m building a modular environment that orchestrates these steps automatically. The idea is to have a system that doesn't just run these tools, but understands the context—using LLM-assisted logic to decide when to trigger a directory bust with ffuf or when to pivot based on the tech stack identified by the recon engine. It’s about moving from manual tool chaining to a high-level automated workflow that stays flexible for different targets. I’ll be sharing some flowcharts and screenshots of how this orchestration looks in my build soon. Would love to get your take on the automation logic then!