@douginamug If it's small enough to grasp the structure and design by inspection as well as its malware-adjacentness, then I would opt for writing one myself while using the found plugin as a template for what things to consider and a potential structure. I would count this as "don't use it" because you're not actually using the plugin on the site.
I think some of the arguments against genAI fall apart in this case. The major one that still applies is how you feel about it - if it makes you feel spiritually icky to look through the code or use any aspect of it, you shouldn't do it.
If that's not an issue, then the cons include:
- not encouraging genAI use: the damage is done, all that remains is not incentivizing others to use genAI - attribution may be a sticking point
- deskilling: not an issue since you're not actually using genAI and are exercising cognitive muscles to extract whatever is useful from it
Finding something useful on the internet and using it as a template or inspiration for your own stuff has always been a cornerstone of website design.
GenAI takes that approach to its deeply unpleasant logical conclusion, but since everything in it is replicating existing patterns of language, I don't think it's necessarily wrong to treat it with the same disrespect that it applies to the rest of the web.
If you want a rationalization, technically you'd be borrowing from the sources that the genAI model was trained on.