If it is a CSS file, then it is your browser that is caching the results, not MODX. While you are working on the site your can hold shift while hitting refresh to try and force your browser to update.
Chrome is notorious for not completely clearing its cache, even with Ctrl-F5. Classic Cache Killer deletes everything and you can turn it on or off with one click.
There’s also the “Disable cache” box on the network tab in dev tools. And also, if you’re using something like Cloudflare it could be cached there too; in which case no amount of local cache clearing will work.
To get the current CSS without caching after modification there is a simple way with setting a version parameter to the file.
At first install the lastModified extra (https://modx.com/extras/package/lastmodified).
Your current path to the CSS in the head section is like:
If you are using a CDN on the site, then you would have to clear the cache there. The suggestion herein for adding version will also correct it there also - that is if you remember to change the file on your end and the time stamp actually changes.