Shadowing Practice: Claude Code Is Wasting Tokens... Microsoft Built a Fix - Learn English Speaking with Video

Kies een oefenmodus

Elke modus opent een volledig scherm oefenruimte.

119 zinnen

Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.

It seems there's a lot of heat with tools and extensions that claim to reduce token usage.

Many of these have been put to the test and they work well.

Now Microsoft just released their own, a free plugin that cut AI coding agent costs by 18 to 31 % in their tests.

And they didn't use a cheaper model or a different agent either.

It works with all the big names, so it's a win for us.

it's called token economizer

and it solves a problem you've probably seen yourself

you ask claude code to fix something fix this it tries a command gets an error

and then keeps running

and burning tokens up to find us a fix token economizer learns from those sessions it remembers how your repo works, removes tools you don't use,

and steps in when the agent keeps making the same mistake.

And the more you use it in the same project, the more tokens you actually save.

So let's install it and see what it actually does.

If you enjoy coding tools the speed of your workflow, be sure to subscribe.

We have videos coming out all the time.

Now I'm going to use

Cloud Code for this, but remember

Token Economizer also supports all the other big names.

First, I'll clone it and install the plugin right here.

We're going to run our git clone.

We're going to install the git plugin from the marketplace and make sure everything is ready to go.

That's installed all super straightforward.

Just keep the clone folder because the plugin runs from there.

Now I'll open one of my existing projects and we're going to fire up Claude Code.

Let's check the status.

All we need to do to check the status here is I'm going to run token economizer status.

This shows what the plugin has learned.

It shows what it's doing and the costs it has already tracked.

Now, quick note here, micro skills are turned off by default.

So I'm going to enable those and we'll circle back.

Then I'll refresh the tool catalog.

I'm going to run here a tool prune, refresh catalog.

Now I'll give Claude Code some tasks.

Let's start super simple.

I'm going to give Claude Code a task, build a unit test.

Very straightforward.

Run it.

Now notice I'm not changing how I use Claude code.

It's the same thing, just on Opus 5 .5, with all the prompts I would normally fire straight at it.

TokenEconomizer just works alongside it.

Now, in a repo where it's already watched several sessions, we can check what it's learned so far.

So here we are.

I'm going to run Microskills.

You can check.

You can run ToolPrune.

Here we can see any repo -specific info it's learned.

In tools, it's identified as unused.

If you install it for the first time, these might be empty.

It needs a few sessions to actually learn what the hell is going on.

And all of that info stays on your machine inside the token economizer folder.

There are really three parts to this.

Now, first up to the plate is called micro skills.

Say you're working on a project that needs a specific command to run its tests.

Claude code, it doesn't know that.

So it tries the usual command, gets an error, try something else and yeah, okay, it eventually gets it.

Great.

Except later when you start a new session, it might make the exact same mistake.

So there we are paying extra tokens, which I would rather not do.

Token Economizer looks at a previous session, all of them, and learns small details about the repo.

Things like which test commands actually work, which environment variables are needed, and where certain files live.

Once something has been confirmed enough times, it can give us that information to the agents at the start of a new session.

So instead of wasting tokens over and over again, the agent already has the answer.

Now next up to the plate is tool pruning.

When you start a coding agent, it can load a bunch of tools into its context, and those tool definitions use tokens,

even if the agent never touches them.

Token Economizer tracks which tools actually get used in your repo.

If a tool consistently goes unused, used, it can stop loading it in a feature session.

And if you need it again, you can just restore it.

Then finally, we go to something called a failure loop intervention.

You've probably watched an agent run a command, get an error, change one small thing and run almost the exact same command again.

Sometimes it just keeps repeating that process.

Token Economizer watches for these patterns.

When it thinks the agent might be stuck, it uses a judge model to check what's happening.

If it detects this loop, it sends the agent a short instruction to try a different approach.

And if the agent still can't recover, it tells you how to stop the turn.

It doesn't just freak out and stop, but does it actually save enough money to even matter?

That's sort of the question.

Yes, it appears to do pretty much that.

Microsoft in UC Berkeley tested

Token Economizer on...

277 SWE benched tasks across six repos using five different agent and model combinations.

And the average cost dropped between 18 .4 % and about 31%.

So the results were pretty good.

In four of the five combinations, tasks' success actually improved.

One saw a small decline, but across all 30 repository and agent model combinations, Token Economizer was cheaper than running without it.

And they even included the plugin's own model calls in those.

Token Economizer isn't completely free to run.

Some of its features use additional model calls.

So those reported savings already accounted for the overhead.

It is open source.

It works with the same agents we already use, and the info it learns stays local.

But I wouldn't expect all of us to see the same results.

Its first public release was in October of this year, and the biggest savings come from working in the same repositories over multiple sessions.

If you're constantly jumping between unrelated projects, there's much less to actually learn from it, or for it, I should say.

If your agent is doing something completely new, there might not be much repeated work to eliminate at all.

So ask yourself, based on the work you do, will this actually be useful?

If you use agents every day on one or a couple core projects, then yeah, this should help.

If you're working on the same repo over and over with Claude Code, Codex, yes, this is going to help.

But if you're building a ton of different projects or you're just playing around, this is not really going to change anything.

100

It's probably not even worth it.

101

So here's what I'd do.

102

Install Token Economizer on the repo you use the most.

103

Run it for a week, then check the status reports like I showed us and compare the costs of similar tasks.

104

If the agent is actually using fewer tokens and whether it's still completing your tasks properly, awesome.

105

It is working.

106

One thing to remember, each agent learns separately.

107

So whatever cloud code learns doesn't automatically carry over to Codex.

108

And don't judge it entirely on the first session.

109

That's why I say run it for a week.

110

The whole point is that it learns from repeated use.

111

If it's saving you money without getting in your way, keep it.

112

If not, you've got the answer.

113

So what it really does is takes a different approach to

114

reducing AI coding costs instead of making the model smaller or compressing your prompts.

115

It looks at the work your agent keeps wasting tokens on.

116

It remembers useful details about your repo, stops loading unused tools, and helps agents recover when it gets stuck.

117

I'm Josh from BetterStack.

118

If you enjoy coding tips and tricks like this, be sure to subscribe.

119

We'll see you in another video.

App downloaden

Alles wat je nodig hebt om vloeiend te spreken

AI UitspraakScoor elke zin

IPA OefeningBeheers elk geluid

WoordenschatBouw je woordenschat op

WoordenspelLeren terwijl je speelt

Scan QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Aanbevolen Video

223 zinnen

9 Insane Claude Mods I Already Can't live Without

Daily ConversationUniversity StudentsWorking Adults

407 zinnen

Why AI Tokens are so Expensive - Computerphile

Daily ConversationUniversity StudentsWorking Adults

207 zinnen

Your AI Agent Starts Every Session Like a New Hire - Killian Carlsen-Phelan, Sonar

Daily ConversationUniversity StudentsWorking Adults

78 zinnen

Woordenschat en spreektips bij deze les

Deze spreekles is gebaseerd op de video “Claude Code Is Wasting Tokens... Microsoft Built a Fix”. Deze woorden komen het vaakst terug: token, agent, economizer, tool, repo. Deze video bevat 119 zinnen en 1344 woorden om na te spreken. Het gesproken deel duurt 7:29. De spreker praat snel, ongeveer 180 woorden per minuut, dus reken op verbonden en ingeslikte klanken. 82% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden; de rest kun je beter vooraf bekijken.

Belangrijke woorden in deze video

15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:

Woord	Uitspraak	Betekenis
token zelfstandig naamwoord	/ˈtoʊkən/	teken
install werkwoord	/ɪnˈstɔl/	installeren, aansluiten
clone zelfstandig naamwoord	/kloʊn/	kloon
cloud zelfstandig naamwoord	/ˈklaʊ̯d/	wolk
skill zelfstandig naamwoord	/skɪl/	bekwaamheid, vaardigheid
loop zelfstandig naamwoord	/luːp/	lus, strop
recover werkwoord	/ɹɪˈkʌvɚ/	terugwinnen
subscribe werkwoord	/səbˈskɹaɪb/	abonneren
catalogue zelfstandig naamwoord	/ˈkæt.əˌlɔɡ/	catalogus, cataloog
prompt werkwoord	/pɹɑmpt/	aansporen, aanmoedigen
straightforward bijvoeglijk naamwoord	/ˌstɹeɪtˈfɔː(ɹ)wə(ɹ)d/	makkelijk, eenvoudig
folder zelfstandig naamwoord	/ˈfoʊldɚ/	hechtmap, map
refresh werkwoord	/ɹɪˈfɹɛʃ/	verfrissen
extension zelfstandig naamwoord	/ɪkˈstɛnʃən/	uitbreiding, extensie
alongside	/əˌlɔŋˈsaɪd/	aan de zijde van

Phrasal verbs die je zult horen

Woord	Uitspraak	Betekenis
come out werkwoord	/ˌkʌm ˈaʊt/	uitkomen
turn off werkwoord		uitzetten, uitschakelen

Zinnen om te herhalen

Korte, volledige zinnen uit de video die je in alledaagse gesprekken kunt gebruiken:

We're going to run our git clone.
Then I'll refresh the tool catalog.
That's why I say run it for a week.
If not, you've got the answer.
We'll see you in another video.

Grammatica in deze video

De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:

Structuur	In de video
Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telt	have been put · you've probably seen · has learned
Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doet	have been put · are turned · is called

Uitspraak om op te letten

De spreker gebruikt 35 samentrekkingen en verkorte vormen, zoals I'm, you're, I'll. Spreek ze kort uit, zoals je ze hoort.

De klanken “sh” en “zh”: combinations /kɑmbɪˈneɪʃənz/, refresh /ɹɪˈfɹɛʃ/, extension /ɪkˈstɛnʃən/, intervention /ɪntɚˈvɛnʃən/, instruction /ɪnˈstɹʌkʃən/
Lange woorden — let op de klemtoon: combinations /kɑmbɪˈneɪʃənz/, intervention /ɪntɚˈvɛnʃən/, consistently /kənˈsɪstəntli/, eliminate /ɪˈlɪm.ɪ.neɪt/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/

Klanken die Nederlandstaligen lastig vinden:

Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: combinations /kɑmbɪˈneɪʃənz/, unused /ʌnˈjuzd/, cloud /ˈklaʊ̯d/, subscribe /səbˈskɹaɪb/, catalogue /ˈkæt.əˌlɔɡ/
/æ/ — opener dan de Nederlandse “e”: catalogue /ˈkæt.əˌlɔɡ/, variable [ˈvæɹ.i.ə.bl̩]
/w/ — met ronde lippen: straightforward /ˌstɹeɪtˈfɔː(ɹ)wə(ɹ)d/, workflow /ˈwɝkfloʊ/

Zo oefen je met deze video

Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
Begin op 0,75× snelheid, spreek zin voor zin na en ga terug naar normale snelheid zodra het makkelijk gaat.
Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als token, install, clone.

Wat is de Shadowing-techniek?

Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.

Shadowing-techniek: lees de volledige stap-voor-stap-gids →

Shadowing Practice: Claude Code Is Wasting Tokens... Microsoft Built a Fix - Learn English Speaking with Video

Kies een oefenmodus

App downloaden

9 Insane Claude Mods I Already Can't live Without

Why AI Tokens are so Expensive - Computerphile

Your AI Agent Starts Every Session Like a New Hire - Killian Carlsen-Phelan, Sonar

The easy way to keep your repos tidy.

Did Anthropic Kill Git?

So I tried Matt's skills...

Give Me 24 minutes, I'll Give You 1,000+ hours of Claude Knowledge

I Tested The Viral Reverse Engineering Repo

JUST $1 For Billions of Tokens?! (DeepSeek v4 Pro)

GitHub Copilot now controls your command line...

The 4-Hour Workweek in a World of AI

STOP Running Code On Your Computer

Woordenschat en spreektips bij deze les

Belangrijke woorden in deze video

Phrasal verbs die je zult horen

Zinnen om te herhalen

Grammatica in deze video

Uitspraak om op te letten

Zo oefen je met deze video

Wat is de Shadowing-techniek?