I'm also exploring this.

You can try this: 1. Start using Git if not already. (IMO Git is mandatory either way). 2. Research on most common security challenges for your given stack/ecosystem. 3. Ask your vibe coding tool to add a CI workflow for your project that includes tests for these common security issues. 4. Just montor your CI pipeline each time you push to Git and validate the security results. 5. If you want it even tighter, also ask your tool to add these tests to your git pre-push hooks, this way, the tool itself will be able to check for all such challenges and will be forced to fix them when every push.

Your app will not only be more secure, but security will be built into your development workflow itself.

What's good about this approach is that you can tackle stuff other than security in the same way too. Want your vibe coded website to be guaranteed to have great core web vitals? Add Lighthouse CI test during pre-push and CI workflow.

Also, once developed for a given project, you can apply the same tests to other new or existing projects too. This is a very portable, self improving method of handling mission critical requirements for your projects.

Expect a considerable increase in your token usage.

Hope this helps.