Build a Claude Code mod that fails closed0% · 0 of 18 carried · progress stays on your account
Build a Claude Code mod that fails closed
From a three-file plugin to four tested mods: a band above the prompt, a guard that holds a production migration until you say yes, a pane that runs a handed command only when you press Run, and a gate that refuses any mod that would fail open. Built from the mods we run every day, with the numbers that tell us when to delete each one.
- Steps8
- Timeabout 3.5 h
- Pricefree
- Updated
The route, step by step
One step at a time: each opens when you pass the reading check at the end of the one before it. A long step counts for more than a short one, and the app goes live on the last one.
- Before you start: Claude Code, Bun and gitweight 1Start here
- Tell a mod from a skill, a hook and an MCP serverweight 1about 10 min
- Count turns in a band above the promptweight 2about 25 min
- Try a permission rule before you write a modweight 1about 15 min
- Hold a production migration until you say yesweight 3about 40 min
- Run handed commands from a pane, one press eachweight 3about 40 min
- Test, gate and install your modsweight 2about 30 min
- Measure each mod and write when to remove itweight 2about 20 min
- Final checkquestions from every stepOpens last
Before you start
What you need
- Stack
- Claude Code · TypeScript · Bun
Skip the build. Start from code that ships
Production-ready code under a one-time licence. Buy it, and start building with the code you bought.
- Pay once
- Resell what you build
- No subscription
The columns, fixes and workshops continue in the community: SEO, AI, and making money with code.
Join on WhopLuke Sidney writes and builds everything here, alone, in the open. lukesidney.me