๐๐น๐ฎ๐๐ฑ๐ฒ ๐๐ผ๐ฑ๐ฒ ๐๐ถ๐ฝ: once Opus 5.5 is your main model, don't let your Fable quota sit idle. Put Fable on call with /advisor.
Run /advisor fable and Claude Code gets ๐ฎ๐ป ๐ฎ๐ฑ๐๐ถ๐๐ผ๐ฟ ๐ผ๐ป ๐๐ต๐ฒ ๐๐ถ๐ฑ๐ฒ๐น๐ถ๐ป๐ฒ๐. Opus 5.5 keeps doing the work and usually calls Fable in at three moments:
โ Before committing to a plan: is it right?
โ When the same error keeps coming back: am I heading the wrong way?
โ Before saying "done": did I miss anything?
Fable reads the whole session and gives advice. Opus still writes the code.
The tree is the full setup. Opus 5.5 on high runs the main session. Three subagents on medium split the rest: one reads code, one edits and runs tests, one looks up docs. Fable waits on the sidelines. Hand the tree and this prompt to Claude Code to set it up ๐
"Set up my Claude Code to match this tree:
1. For the three subagents, reuse fitting ones from ~/.claude/agents and .claude/agents, and propose new ones only for missing roles. Set each to model: opus and effort: medium. Leave any subagent that already sets a different model alone, and list it.
2. Set the main session's default effort to high with effortLevel in ~/.claude/settings.json.
3. Check for environment variables that turn the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, or DISABLE_TELEMETRY and anything else that stops flag fetching) and for CLAUDE_CODE_EFFORT_LEVEL, which overrides every subagent's effort. Report them; don't change them.
4. Add one rule to ~/.claude/CLAUDE.md: ask the advisor before committing to a big plan, when the same error shows up a second time, and before calling a long task done.
Show me the changes first. Don't edit any files yet."
https://t.co/FaFivbb9Pj
Claude Coders: run this Opus 5.5 instruction cleanup prompt *NOW*.
'/claude-api prompt-audit'
Optimizes your skills, AGENTS.md, CLAUDE.md and removes anti-patterns that restrict Opus 5.5.
The results are amazing. Best 5 mins you'll spend.
From @RLanceMartin.
Try these in your first Opus 5.5 session:
โ Hand over a whole task. Define "done" and when to check in.
โ Drop "think carefully". It always thinks first.
โ After a long run, check what it needs to go further.
Our playbook: https://t.co/h4Vz9BIl0z
Anthropic engineer:
"99% of people use Claude Code like Google, and only 1% are running swarms of self-learning Claude agents
I'm running 100+ agents in a loop. I have Chief agent, PM agents - they manage the whole team"
in a 30-minute workshop, an Anthropic engineer revealed how to get max value from Claude Code at min. cost
this is worth more than another $500 vibe-coding course
watch today, then read how to build self-improving agentic systems with Fable in the article below
SpaceXAI engineer, Lauren Tan:
"GrokBot is the most powerful agentic tool we have ever shipped, but only 1% of users use it correctly|
at SpaceXAI, I'm running a team of 15+ GrokBot agents. I have a Chief of Staff agent, 3 managers and 11 workers - that's the new engineering setup in 2026"
In a 1-hour talk, a SpaceXAI engineer reveals how to get 100% of every agentic tool you are using
worth more than a $500 agentic course on the internet
skip Netflix and watch today, it will change the way you use GrokBot forever, then read the article below
@ariaghora harus sungkem sama ini orang mas. dia tadi bilang loh cobain selesain soal leetcode hard tanpa AI
terus profilnya ya gtu, grinding nya luar biasa. salute ๐ซก
@FaadhiIlham@mydearestnoona mau jd public enemy ceritanya bang? emang kenapa kalau ada yg ngoding pake AI lalu dibilang skill issue?
kalau ini blm era AI, msh era nya stackoverflow, terus yg ngoding nengok stackoverflow dibilang skill issue?
if you good at what your do, good for you. stop judgement ppl!
We're adding support for AGENTS.md to Claude Code.
Starting today in version 2.1.277, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md.
You can toggle this behavior in /config.
Spotify's engineering team cut Claude Code token usage by 90% with a two-model routing approach they call Portal. The mechanism is worth understanding because it's not prompt engineering, it's hard blocks at the architecture level.
Two cheaper "assistant" models handle the tasks that don't need the expensive model: opening files, writing repetitive code, boilerplate. The expensive model only touches novel reasoning. Files over 350 lines get blocked from the expensive model entirely, not suggested away from it, blocked.
They tried rules-as-instructions first. It didn't hold. Engineers (and the model) found ways around soft rules. Hard blocks at the routing layer worked where prompt-level guidance failed.
90% token reduction is a big number. The implication is that most of what people use frontier models for in a coding workflow doesn't actually require frontier-level reasoning. Routing to capability level rather than defaulting to the best model available is a legitimate architecture pattern.
Article is worth reading in full.
https://t.co/4Kd8y24ILo
Do these 4 steps to stop Fable 5.1 from wiping out your weekly credits:
1. Set /effort to low
2. Run /claude-api cost-optimize to find the biggest wastes
3. Run /claude-api prompt-audit to clear old junk
4. Run /claude-api migrate this project to claude-fable-5-1 to update old model ids
You wonโt have to worry about wasting tokens anymore.
5 Fable 5.1 optimizations you can use *NOW*.
1. Set effort to 'low'
2. Run '/claude-api cost-optimize'
3. Run 'claude-api prompt-audit'
4. Change effort mid-conversation w/o cache hit
5. Update Fable 5.1 API config w/ 'claude-api migrate'
From @RLanceMartin
some tips for Claude Fable 5.1
Try Fable 5.1 at low effort | Fable 5.1 at low effort is often competitive with Opus and Sonnet on $ / task while scoring higher. on CursorBench 3.2.0, Fable 5.1 at low effort is at parity w/ Fable 5 at high effort at a third of the cost.
Prompt cache reads are 4x cheaper for Fable 5.1 | cache hits dropped from $1.00 to $0.25 / MTok. if you are using prompt caching, Claude Console can monitor your prompt cache hit rate. also run โ/claude-api cost-optimizeโ in Claude Code to run diagnostics on your prompt cache configuration. see pricing:
https://t.co/d5sEMwmT9H
Simplify your prompts | remove verification rituals, emphasis boosters, scratchpad scaffolds, stale few-shot examples, or contradictory rules. in Claude Code, run โ/claude-api prompt-auditโ to inspect prompts or skills for common anti-patterns. see our prompt guide:
https://t.co/QgJLf0r0hE
Change effort mid-conversation w/o breaking the prompt cache | Previously, mid-conversation changes to effort invalidated the cache. see docs:
https://t.co/tAJUJBCNXk
for migrating to Fable 5.1, see the migration guide and run "/claude-api migrate" in Claude Code to help update API configuration to use Fable 5.1.
https://t.co/eDcnAEUStM