Veyro

Claude tricks most people don't know. Prompts, settings, workflows

[Veyro @0xVeyyro]

yeah. giving grep its own haiku roommate was the move that actually moved the needle.

[Veyro @0xVeyyro]

most people run Opus on everything and wonder why their usage melts by noon

you don't need Opus to grep a file. here's the setup that fixed it for me

claude --model sonnet --advisor opus

Sonnet runs the session and writes the code. three Haiku subagents do the grunt work in parallel:

search → maps the repo, read-only
grep → finds every call site in its own context
audit → checks the diff in a throwaway worktree, never touches my branch

Haiku runs all of that at 0.05x Sonnet's price. the cheap model does the boring 80%

Opus doesn't sit in the loop. it's an advisor. it only wakes up 3 times:

before a plan locks
when the same error hits twice
before it ships, to sign off on the diff

that's the whole trick. stop paying the smart model to read logs

one catch people miss: the env var that sets the subagent model is just a default. drop model: haiku into each agent file or they'll quietly run on Sonnet and you're back to square one

prompt to set it all up is below. paste it, read the diff before you say go

it's been running my repo all week. main context stays tiny, bill dropped, and i stopped babysitting it

[Argona @Argona0x]

https://t.co/uFcQbivrbz

[Veyro @0xVeyyro]

@Synthexfr Every token costs twice is the key takeway.Reset more often.Great cut

[Veyro @0xVeyyro]

@0xJeyx Love the loop Err on the side of more evidence

[Veyro @0xVeyyro]

@AIDuckLabs This is so useful.Instant normal maps for pixel art - the lighting difference is crazy

[Veyro @0xVeyyro]

@bubosees Yeah, that line is the whole reason I trust the setup. Autonomy with a hard stop.

[Veyro @0xVeyyro]

f*cking insane. you can give Claude Code a night shift: 1 rule, your laptop shut, and Opus 5.5 has a stack of tested fixes waiting for you by morning

the AI chief of staff post above hit 350K views overnight. here's the dev version, and it's 2 things already in the Claude Code docs: claude -p and a cron job

no junior on nights. no $200K hire. it costs whatever you cap it at with --max-budget-usd

you give the goal, it does the steps, you only make the calls

the rule:
"clear my issue backlog. reproduce before you fix. never touch main. merge nothing without my yes"

the night:
→ 11pm Opus 5.5 reads every open issue and splits the work into jobs
→ 12am Haiku 5.5 subagents try to reproduce each bug in their own worktree, dupes and stale ones get cut
→ 1am Sonnet 5.5 writes a fix for every bug it could reproduce, 1 branch per issue, tests included
→ 3am a reviewer that never saw the writer's chat reads every diff: PASS or FAIL
→ 5am every FAIL gets 1 more try, then it's parked with a 1-line note
→ 8am you open summary.md with your coffee

honestly the "park it" step is the whole thing. an agent that can't say "i couldn't fix this" ships garbage straight to your main branch

and it runs again every night at 11pm. it never forgets to start

312 open issues → only the bugs it can reproduce → only the fixes a second model passes → 0 merged without you

it opens branches. it never merges

someone's backlog is already getting cleared while they sleep

the full setup is below ↓ free, steal it

[Argona @Argona0x]

https://t.co/uFcQbivrbz

[Veyro @0xVeyyro]

@bubosees Grok is as shameless as ever

[Veyro @0xVeyyro]

@andreysuperior So Space Bunny was just MiniMax this whole time?Wild

[Veyro @0xVeyyro]

@alxqwrk One afternoon witch Claude and the ads are gone They should be scared

[Veyro @0xVeyyro]

@Klonzu the compiler isn’t the brain, what you feed it is. this pipeline actually makes sense

[Veyro @0xVeyyro]

@Synthexfr 400 lines every session is brutal. moving the procedures to skills is the right call

[Veyro @0xVeyyro]

@itsarcvale @t4t5 same hash 17 years later is wild. now do this for every wallet I run

[Veyro @0xVeyyro]

everyone's counting the 300 agents.

nobody's asking who checks their work.

that's the part that actually matters. 300 agents with nobody checking = 300 ways to merge garbage at once.

the fix is stupid simple. a second model that never saw the code being written reads the diff and says yes or no.

1 agent writes:

claude -p "Fix issue #142. Commit to branch fix-142."

a cheap Haiku 5.5 checks:

git diff main..fix-142 | claude -p --model haiku "You didn't write this. Does it fix issue #142? PASS or FAIL + 1 reason."

FAIL → back to the writer
PASS → merge

that's it. it works because the checker has zero reason to defend the code. it didn't write it.

and Haiku 5.5 is $0.10 per 1M input tokens. checking 300 diffs costs less than your coffee.

for the merges that can break prod, swap haiku for opus.

checker prompt in the reply. save this before your agents start shipping

[Bober_smart @Bober_smart]

https://t.co/WRvaPXgqIa

[Veyro @0xVeyyro]

@alxqwrk Try it with something personal. Portrait, old photo, random screenshot. The output changes a lot depending on the image.

[Veyro @0xVeyyro]

It is becoming f*cking dangerous: 1 prompt to Claude and it built a lab that turns any photo into a living 3D data structure

1 HTML file. No install. No backend.

Upload an image and it rebuilds it as:
→ a rotating ring of dot-matrix blocks sampled from your pixels
→ thousands of spikes, taller where the image is brighter
→ a web of threads connecting the darkest points
→ the original photo, redrawn as halftone dots underneath

The camera cuts every 6 seconds. Overview. Dive into the spikes. Skim the ring.

There's a record button. It exports the whole thing as a video.

This one is a diagram of diseases I found on Pinterest.

The prompt is below. Save it before you need it.

[Bober_smart @Bober_smart]

https://t.co/WRvaPXgqIa

[Veyro @0xVeyyro]

@maixbt Exactly. Screenshots die in 3 seconds. The record button turns it into something you can actually share and drop anywhere.

1 file is the other half of it zero friction.

[Veyro @0xVeyyro]

@andreysuperior One evening to rebuild a paid feature is wild. Companies are going to hate this

[Veyro @0xVeyyro]

@andreysuperior One prompt to reverse-engineer paid features is wild. How solid is the verification step in practice?

[Veyro @0xVeyyro]

@Richix01 This is the comment the original post needed. OS matters more than the prompt