DESIGN.md:

> Each rule below is enforced mechanically by the skill, not left to vibes.

> R1. Repo docs are the memory; not in HANDOFF.md = didn't happen

SKILL.md:

> Not in docs/HANDOFF.md = didn't happen. Refuse to judge results that exist only in conversation or builder chat output.

"Mechnical enforcement" just means "prompting the LLM a bit extra" these days? It (still) amazes me how much effort and tokens we expend on what could and should be a two line script...

> freezes the gates

LLM-written readmes love to use inscrutable jargon that means nothing outside of the context window that birthed it.

I actually just started doing this by having Fable roleplay as Jeff Dean and to use Codex as Sanjay driving the implementation and have them go back and forth. Works really well and it’s cool to see AI pair program

US Govt reduces Fable Tokens by 100%.

Who's gonna tell them...

I do exactly this with awman workflows: https://github.com/prettysmartdev/awman/blob/main/docs/05-wo...

You can use any agent and/or model for each step and share context between them.

I guess that didn’t age well

Fable will do this itself, by spawning Opus/Sonnet subagents to do easy work.

Reduce Fable tokens by 80%, simply by not using it!

> I am fairly convinced this is the shape serious agent work keeps converging toward.

"this" being "plan with expensive model, implement with cheap model".

Anyone who follows HN would be hard-pressed to disagree; this architecture is re-invented twice monthly.

https://www.facebook.com/groups/vibecodinglife/posts/1946207... https://github.com/openai/codex/discussions/10628 https://build5nines.com/stop-burning-premium-requests-how-to...

> Not because it is aesthetically pleasing. Because every other shape eventually runs into the same boring failures: context rot, self-grading, goalpost drift, and merge chaos.

Actual failure isn't boring. But struggling through a generated software project that celebrates its own genius and doesn't have a single self-critical or genuinely reflective thing to say...at least watching paint dry I might get giddy off the fumes.

I'm not interested in critiquing the project itself, either, you'll just run that through a model, too.

yes I'm using Fable to inspect, generate plan and architectural docs then using Gemini to implement then have Fable review, find bugs. saving lots of usage.

ANNNNNND it's gone. Guys, I found a way to reduce Fable token usage 100%. You can find it here: github.com/USGov/idiotic-overreach.

Fool me once. Fool me twice. Fool me thirty three times and here we are trying lucky number 34.

Reducing token usage is this year's "one weird trick". It doesn't make sense on the face of it.

Even if one discovered something that millions (billions?) of dollars of AI compute and the best statisticians in the world was not able to find via exhaustive research, domain search and training... what do you think are the chances this won't be folded into the next update of every model, making the rigmarole moot?

Extraordinary claims require extraordinary evidence and technology-shattering innovations in AI are not know to come from a markdown.

I know how to reduce Fable tokens by 100% ; https://www.anthropic.com/news/fable-mythos-access

Last night I switched back to Codex for a minute having burned through my tokens for the week with Fable and oh boy I had a terrible experience. Running in circles over simple problems (which I ended up solving myself, like a peasant) and running "terraform apply" several times despite several instructions all over the place to never do that. The performance difference was stark.

Reduce fable token usage even more by not using it. What a clever idea, op! Wow.