How do you make Opus cut the fluff and reply like a human?

Reading through the output of Opus and trying to decipher it, sometimes feels exhausting. There's so much fluff and noise, but the worst is the "painfully AI-generated" words and phrases that it uses, which no human on earth would use: Furthermore, delving deeper into the implementation reveals that mapping over this collection will ultimately yield a brand new array. It is crucial to remember that a well-defined repository boundary is a testament to clean architecture. This was a big issue in Opus 4.8 which seems to be slightly improved in Opus 5. How do you work around this? Do you use custom agents or skills, asking to remove the noise and fluff? Do you use some kind of 3rd party framework (e.g. caveman)?