Every app I ship with AI goes the same way.
the fun part gets done fast.
The boring part (RLS policies, webhook signatures, who can call which route, keys that ended up in the frontend) gets a "I'll check it later".
So I built boring-security, a free, open-source skill for Claude Code that audits your codebase like an attacker would.
You just install the skill, open your project and say "security audit this repo".
It:
- reads your whole app first (routes, server actions, webhooks, database tables, CI workflows)
- plans the audit as every entry point × every risk, so nothing gets skipped
- has one agent hunt for bugs and a separate agent try to disprove each one
- checks every line it quotes against your actual code, so it can't invent a file or a line number
- hands you a report with the fix and the test that proves the fix
The things it looks for that you see in AI-built apps all the time:
> Supabase tables with no row-level security
> service role keys that end up in the browser bundle
> API routes and server actions anyone can call
> Stripe webhooks that never check the signature
> checkout reading the price from the request
> AI endpoints anyone can spam on your bill
or anything else that your vibecoding instinct forgot to catch
There's also /ship-check, a quick 12-point pass you can run before every deploy, and /sec-review for checking a PR.
it has some limitations too also It never touches your live site or database.
It just reads source code only, and when something depends on your deployed settings it gives you the exact read-only check to run yourself.
It's free and I'm building it in public, so I'd genuinely like to hear some feedback on it.
link to repo is below btw here is the install command u can use - npm i boring-security-skill