Tag the randomized User-Agent without disabling randomization (e.g. -ua-tag)

### Summary Nuclei randomizes the `User-Agent` on each HTTP request, which is useful for avoiding trivial UA-based filtering. However, there is **no way today to attribute a scan's traffic** (tag it with a scanner name, run/job id, etc.) **without giving up that randomization**. The only current option is `-H "User-Agent: <value>"`, which **replaces** the random UA with a single static string on every request — so you have to trade away per-request randomization to get attribution. ### Request A flag that **appends** a caller-provided tag to the randomized UA — keeping per-request randomization while still tagging every request: ``` nuclei -u https://example.com -ua-tag "myscanner/1.0" # User-Agent: <random UA> myscanner/1.0 ``` ### Why - Attribute / allowlist your own scan traffic on the target side. - Audit trails — identify scan requests in target logs. - Without losing the benefit of User-Agent randomization. It would tag only the auto-generated UA; requests that explicitly set a `User-Agent` (via `-H` or a template header) would be left unchanged.