Launch offer: everything is 100% off. Download any skill free, no sign-up. Get the skills
For Claude Code, Claude.ai, Cursor, Codex & more

AI built it. Something broke, leaked or cost you.

Fix it in minutes, then make sure it never happens again.

TechFix is a pack of small skills for your AI coding agent, one for each thing that goes wrong once AI-built code goes live.

No installs No accounts Works offline Free during launch
> check this before I deploy
broke-after-deploy scanning the code that runs in production…
$ npm run build · ok
 
NOT SAFE TO SHIP 2 things will break in production.
 
1 Finding API calls go to http://localhost:4000
Evidence src/lib/api.ts:3
Impact every request from the live site fails
Fix read NEXT_PUBLIC_API_URL (diff ready)
2 Finding imports ./components/header, file is Header.tsx
Evidence app/page.tsx:2
Impact the Linux build stops: "Module not found"
Fix match the file name (diff ready)
 
Can't see your hosting dashboard. Check DATABASE_URL
is set for Production.
apply 2 diffs? [y/N]
Example report. Your findings depend on your code.
Works with Claude Code Claude.ai Cursor Codex Any SKILL.md agent
What goes wrong

Once AI-built code goes live,
three things go wrong.

It breaks, it leaks a key, or it runs up a bill. And the agent that built it often said "done" first. Each one has an error people search for at the worst moment. We wrote the fix for each, and a skill that does it for you.

It leaked a key

A secret ended up in git, a bundle or a public repo.

It cost you

An open endpoint, a loop or no cap ran up a bill.

It said "done"

The agent said it works. The tests say otherwise.

The skills

One skill for each emergency.

Each one starts with the emergency you have right now, then makes sure it can't happen again. You can tell what each one does from its name.

$9 Free

Broke After Deploy

Before it breaks, or after

About to deploy? It finds what will break in production before your users do: localhost URLs, missing env vars, files the server can't write, imports that only work on your laptop, and 30+ more.

Already broke? Paste the error: it finds the cause, then checks what will break next.

> check this before I deploy
Download free $9 How it works
$7 Free

Key Leaked

Got a "your key was exposed" email?

It finds every secret in your code, git history and the JavaScript you ship to browsers, and says how bad each one is.

Then it walks you through revoking and replacing it, with exact steps for 19 providers.

> I pushed my .env
Download free $7 How it works
$7 Free

Bill Spiked

AI or cloud bill jumped?

It finds the uncapped calls, loops and open endpoints that caused it, and adds the limits.

Then it gives you a spending-cap checklist for each provider in your code.

> my OpenAI bill spiked
Download free $7 How it works
Free

Prove It Works

Before your agent says "done"

It runs your tests and build and shows the real output.

If anything fails or breaks a project rule, the agent has to say so and fix it.

> prove it works
Download free How it works
Ship Check bundle

One command before you ship $19 Free

/ship-check runs every check and gives one verdict: safe to ship, or what will break, leak or cost you.

  • All four skills included
  • Cross-checks between them: a leaked AI key next to an uncapped call is critical
  • A local saves ledger, so you can see what it has caught
How it works

Every report reads the same way.

When something is on fire you don't want an essay. Every skill gives you the verdict first, then only what you need to act.

1

The verdict comes first

One line: safe to ship, or what will break, leak or cost you. Detail comes after.

2

Every finding has 4 parts

Finding, Evidence (file and line), Impact, and Fix. Nothing vague like "consider reviewing your config".

3

Read-only by default

The skill reads your code. It doesn't touch it.

4

Fixes are diffs you approve

Every fix is shown as a diff first and applied only when you say yes.

5

It says what it can't see

Your hosting dashboard, live database or real traffic. It tells you exactly where to look instead of guessing.

key-leaked · example finding1 of 1
EXPOSEDAn OpenAI key is in your client bundle. Rotate it now.
Finding

Secret OpenAI key behind a browser prefix: NEXT_PUBLIC_OPENAI_KEY

Evidence

app/chat/page.tsx:12 and .next/static/chunks/…js (sk-p…9f2Q)

Impact

Anyone who loads your site can read this key and run requests billed to you.

Fix

Rotate the key first, then move the call to a server route: - const key = process.env.NEXT_PUBLIC_OPENAI_KEY + const res = await fetch('/api/chat', opts)

Can't seewhether the key was used since. Check the provider's usage page for that key.
Measured results

Tested against planted problems.

Each skill was scored on blind tests written by someone who never saw it, next to what you'd use without it.

Broke After Deploy

Blind test, JavaScript and TypeScript projects: 33 planted bugs

Broke After Deploy
33 of 330 false alarms
Plain Claudesame test, no skill
94%11 false alarms

Key Leaked

Blind test: 35 planted leaks

Key Leaked
35 of 350 false alarms
gitleaksa popular free scanner, same test
60%25 false alarms

Bill Spiked

7 blind bill-spike emergencies (repo + usage data)

Bill Spiked
6 of 7fully solved, 0 wrong cap claims
Plain Claudesame cases, no skill
1 of 74 wrong claims about provider caps

"Fully solved" means the right cause, the right stop-the-bleeding steps, correct provider cap steps and a working fix. Prove It Works is free, so it has no scoreboard here: it makes your agent verify its work every time, not only when you remember to ask.

Install in 30 seconds

Unzip. Start a session. Ask.

Each skill is a folder with a SKILL.md file and small scripts that use only Python's standard library. Nothing else to install.

01

Unzip into your skills folder

  • Claude Code: ~/.claude/skills/, or .claude/skills/ inside your project
  • Claude.ai: Settings > Capabilities > Skills, then upload the zip (for Ship Check, upload all five: broke-after-deploy, key-leaked, bill-spiked, prove-it-works, ship-check)
  • Ship Check bundle: one zip with all five folders; unzip it into the same skills folder
  • Other agents that read SKILL.md files: their skills folder
$ unzip key-leaked.zip -d ~/.claude/skills/

Full install guide for Claude Code, Claude.ai, Cursor and Codex

02

Start a new session

Your agent picks the skill up on the next session and loads it when your problem matches.

$ claude
03

Describe the problem

Paste the error or the alert, or say what you're about to do. You get the verdict first.

> my site broke after deploying
Pricing

Cheaper than the hour it saves.

Buy the one you need right now, or everything at once.

Single skill

$0 $7 to $9

Fix the one problem you have today. Yours to keep.

  • Broke After Deploy$9 Free
  • Key Leaked$7 Free
  • Bill Spiked$7 Free
  • Prove It WorksFree
ONE COMMAND

Ship Check bundle

$0 $19 launch offer

/ship-check runs every check and gives one verdict before you ship.

  • All four skills
  • Cross-checks between skills
  • Local saves ledger

All access

$0 $29/yr launch offer

Everything, plus every new skill.

  • Ship Check and all four skills
  • Every new skill we ship

Launch offer: 100% off. Every skill and the bundle are free to download right now, and what you download is yours to keep. Checksums

FAQ

Questions, answered.

Which agents does it work with?

Claude Code, Claude.ai, Cursor, Codex and other agents that read SKILL.md files. Each skill is a folder with a SKILL.md file and small Python scripts. Broke After Deploy is built for JavaScript and TypeScript projects (Next.js, Vite, React, Node, Express).

Does it work offline?

Yes. The checks use only Python's standard library and make no network calls, so they run without internet. Your agent still needs its own connection to its model. Key Leaked never tests whether a key is live; it assumes an exposed key is live and tells you to rotate it.

What if a skill doesn't help?

During the launch offer everything is free, so there is nothing to refund. Tell us what went wrong and we will fix the skill. Once paid plans start, refunds are no-questions.

Does my code or my secrets leave my machine?

Not through TechFix. In Claude Code, Cursor, Codex and other local agents, the scripts run on your machine, make no network calls, send no telemetry and need no account. Key Leaked never prints a full secret, in chat or in any file. Your agent reads the report the same way it reads your code. In Claude.ai, skills run in Claude's own sandbox on the files you give it.

Does it change my code?

Not without asking. Every skill is read-only by default. Fixes come as diffs and are applied only after you approve them. With your OK, a skill adds one line per run to .techfix/ledger.md so you can see what it caught; delete or gitignore it any time. Key Leaked never rewrites your git history; it shows you the commands.

Couldn't I just ask my agent?

You can, and for many things it does fine. On the same blind test, plain Claude caught 94% of the planted deploy bugs with 11 false alarms; Broke After Deploy caught all 33 with none. The skills add scripted checks, a list of known causes, and provider steps with sources, so the answer doesn't depend on what the agent remembers that day.

What can't it see?

Anything outside your code: your hosting dashboard, live database, real traffic, provider dashboards and invoices you haven't pasted. Each report says which of these matter for your problem and exactly where to check them.

Stay in the loop

Hear when new skills ship.

Leave your email and we'll tell you when new skills land.