Last week someone on the r/ClaudeAI subreddit asked what AI "lifehack" people still don't seem to know about. It got over 400 replies, and the top answer had about three times more upvotes than anything else.
Instead of asking the AI to do a task, ask it to build a small program that does the task.
In the commenter's words, "next time you do it it'll cost no tokens".
The truth is a lot of the things we ask Claude or ChatGPT to do need no judgement at all, and could be a script (a short program that runs a fixed set of steps) instead.
01 / 05
Why it's worth doing
- It's free to run. You spend tokens building it once, then nothing on every run after that. One reply pointed out this also protects you if AI prices go up.
- You get the same result every time. AI models have a little randomness built in, so the same request can be handled differently each time. A script does exactly what it did last time, and you can see how it did it.
- It makes fewer mistakes. AI models are unreliable at maths and at reading dense tables of numbers, while code just follows the rules it's given.
- Your data can stay on your computer. Give the AI a few made-up rows with the real column names, let it build the tool, then run it on the real data yourself. A government worker in the thread builds tools this way because their data isn't allowed anywhere near AI.
- Other people can use it. A single web page works for a colleague who has never opened a terminal and doesn't have a Claude account.
- It's easy to change later. Ask for the program that makes the chart rather than the chart itself. Next month you can rerun it with new data, or get the AI to tweak what it shows.
Anthropic has made the same argument. In a November 2025 engineering post they showed that letting the model write code to move data between tools took one job from about 150,000 tokens to 2,000.
02 / 05
What it looks like in practice
I use this for my monthly bank statements. Giving Claude a folder of PDFs each month burned a lot of tokens, and it often misread the pages full of numbers.
Now a script pulls the transactions out of each PDF into a CSV (a plain text spreadsheet), and Claude reads that instead. It saves tens of thousands of tokens a month, and the numbers are easy to check.
Some of the best examples from the thread:
- Shipping labels. A small business owner drops an invoice PDF into a desktop tool and gets back label PDFs sized for their printer. They'd asked Claude to do it a few times, then asked it to make a program instead.
- Checking web pages on every screen size. A developer was paying the AI to resize a browser and screenshot each width, and it still missed things. They had it write a Playwright script (a tool that drives a browser automatically) to catch overflowing boxes and tiny buttons with no AI involved, then wrapped it in a skill so the AI uses it without being told.
- A teacher's admin. Google Apps Script for repetitive Google Classroom jobs, and Python for quiz questions they set over and over.
- Volleyball highlights. Someone who films matches has an app that picks out the best moments from a full recording and tags them, all running on their own graphics card. They say they use about 10% of their Pro plan.
Outside the thread, Simon Willison has built over 150 single-file HTML tools in about two years, nearly all written by AI.
03 / 05
Skills still spend tokens
Claude Skills feel like the answer to all this. You write a process down once, and Claude follows it the same way whenever it's needed. ChatGPT has the same feature, also called Skills.
Having a repeatable process feels efficient. But a skill that's only written instructions still has the AI doing the work on every run, reading the instructions, thinking, calling tools and checking the results, and all of that costs tokens.
A skill telling Claude how to read my bank statement PDFs would still have it reading every page, every month. It would just be more consistent about it.
Skills can also hold scripts if you want to combine some code with AI judgement. The script runs as code and only its result goes back to the AI, which is how the Playwright example above works.
So the choice depends on how much the task needs AI. If it doesn't need it at all, a standalone program is better, because it runs without opening Claude and costs nothing.
If the AI needs to decide when to run the tool or make sense of what comes out, put the script inside a skill. Keep instruction-only skills for the parts that need judgement, like drafting a reply in your tone of voice.
04 / 05
When to keep the AI
It only works for tasks with clear rules. If the job needs judgement, like summarising a call or deciding which lead to chase, you'll still want the model, so the best setups split the work. The bank statement script does the extraction, and Claude only explains what the numbers mean.
Programs can break when a website changes or a library the script relies on gets updated. Keeping tools small helps, and paying for one repair every twenty runs still beats paying on every run.
It also has to be worth building. Now that AI does the building in an hour ten minutes, far more tasks are worth automating, but a one-off is still a one-off.
You're also running code you didn't write, so point it at a sample of your data first and check the first few results by hand.
05 / 05
How to start
- Find the repeat. Anything you've asked an AI to do more than twice with different inputs, like renaming files, cleaning a spreadsheet export or pulling numbers out of PDFs.
- Change the prompt. Ask "build me a program that does this" instead of "do this", and say how you want to run it, whether that's a button on a web page or a file you double-click.
- Use a coding agent. Claude Code or Codex pointed at a folder on your computer is the easiest route, and Python suits most jobs. If you'd rather avoid the terminal, ask Claude or ChatGPT for a single HTML file and open it in your browser.
- Keep it tidy. Ask for a one-line summary at the end of every run so you can see what it did, and keep all your tools in one folder. Once a tool is working, turn it into a skill so the AI reaches for it without being asked.
Pick one thing you asked AI to do twice last week, and ask it for the program instead.

Written by
Kieran Ball
Co-founder, Create With

Written by
James Devonport
Co-founder, Create With
The Create With Briefing
Get the next edition first.
Real-life use cases, the tool changes that matter, and the best events near you. Free, every Tuesday, to 8,600+ readers.