Not really?
I have some custom skills/MCP servers I use:
one MCP server for using https://usefeyn.com/blog/pulpie-pareto-optimal-models-for-cl... ran locally so that reading web pages is cheaper and uses up less context
One MCP server for doing automated code quality checking, using Valknut, Jscpd, and Lizard to output scores, combine/aggregate them. That's then give to the model so that it can see if there's a mess of code dupe or if there was significant architectural regression. It's allowed to say "This is worth it" but it ground it a bit and stops really stupid, short sighted, hacked-in features
Another uses https://github.com/thejens/id-token-nicer so that the model doesn't bork a big ID without being noticed. It's told to translate in and out of that as necessary.
I had it write it's own skill for making sure to follow some sane commenting/style guides per language, that way it doesn't just give me massive files with no comments.
Finally, a last one lets Antigravity or Codex call out to local models as workers, for long running background tasks where a cheap, dumb model is fine. Saves on overall token usage.
I also have a few skills from the internet setup. https://github.com/AlmogBaku/debug-skill being the most important one.
On top of that, the way people work is notable: Do you use worktrees for agents? Why/why not? Do you have only one subscription? What level? I'm using both Codex at $20/mo and Antigravity at (promo) $5/mo right now. Antigravity's TOS says you MUST use their harness, which informs some of my skill setup/workflow. Do you make your agents.md self modifying, write it yourself, or not use one at all? Do you use a sandbox or YOLO it?
Even just how you prompt matters. On Antigravity/Gemini, I can give it a big list-o-TODOs and have it make a very detailed implementation plan itself, carry it out, and generally do the thing, all unsupervised. Codex, from what I have experienced, isn't as good at that. Doing the planning as a separate step, writing to a file, then telling it to step-by-step it with commits for each step makes it work okay again though.
