This video walks through four free repositories that cut Claude Code token usage on both input and output: RTK (a CLI proxy that trims bash command output), Headroom (a wrapper that compresses repetitive conversation history), Ponytail (a skill that makes agents write leaner code), and Graphy (which turns a codebase into a queryable knowledge graph to avoid grep back-and-forth).
Eric Tech15 minTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, plan, edit, verify, summarize, and route the next task to the right tool.
New playlist item from Eric Tech; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to diagnose where an AI coding agent wastes tokens (noisy shell output, bloated conversation history, over-verbose generated code, and repeated codebase searches) and install the right free proxy or skill to cut each source.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect
02Plan
03Edit
04Verify
05Review
06Route
Deep lesson
Turn this video into working knowledge.
3,417 cleaned transcript words reviewed across 918 timed caption segments.
Thesis
4 Free Repos That Cut Claude Code Token Usage teaches a practical codex + claude workflows move: This video walks through four free repositories that cut Claude Code token usage on both input and output: RTK (a CLI proxy that trims bash command output), Headroom (a wrapper that compresses repetitive conversation history), Ponytail (a skill that makes agents write leaner code), and Graphy (which turns a codebase into a queryable knowledge graph to avoid grep back-and-forth).
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:34
RTK trims shell noise
“by 60 to 90%. And the way how that works is whenever we have large function model here sending a bash commands right try to run a bash command or shell script for example get status let's say...”
RTK is a CLI proxy hook that sits between the CLI and the large model; when the agent runs a bash command like git status that outputs ~600 tokens, RTK runs it and trims the output down (roughly to ~300) before it reaches the model, claiming 60-90% savings on command output. Install with a copied command, then `RTK init` globally (default target is Claude Code, also supports Codex and other agents), and check savings with the `RTK gain` command. Install RTK globally against Claude Code, run a few bash-heavy tasks, then run the RTK usage command to record how many tokens it reports saved before and after.
6:25
Headroom vs /compact
“going to type in headroom. Okay? And we're just going to type in wrap and we're just going to wrap whatever AI agent you're using. If you're using codecs, if you're using Hermes agents, whatever it is, you...”
Because the model has no memory, every turn resends the whole conversation, so cost balloons by the 20th or 40th message. Headroom is a proxy you install (npm or pip/uv) and run as `headroom wrap claude`; it intercepts each request and removes repetitive/redundant history instead of summarizing like /compact, so it avoids losing important constants and statements that summarization drops. `headroom dashboard` shows before/after token totals. Wrap a Claude session with `headroom wrap claude`, hold a multi-turn conversation, then open the headroom dashboard and note the before/after token percentage saved.
11:03
Ponytail + Graphy on output
“before I show you the last skill, one thing that I want to talk about here is if you're looking to master AI agents, building automations and building real SAS products and I highly recommend to check out...”
Ponytail is a skill that makes the agent behave like a lazy senior engineer, producing the same app with far fewer lines of code, which cuts generation tokens and review time (1000 lines ~ 1000 tokens vs 100 lines ~ 100 tokens). Graphy attacks the other output cost by turning a codebase or docs into a queryable knowledge graph so the agent reads a single map file instead of burning tokens on repeated grep/bash searches to locate functions and files. Install Ponytail as a Claude Code plugin at project scope, then ask it to build or simplify a small app and compare the line/file count against a build done without the skill.
01
Inspect
Start with this video's job: This video walks through four free repositories that cut Claude Code token usage on both input and output: RTK (a CLI proxy that trims bash command output), Headroom (a wrapper that compresses repetitive conversation history), Ponytail (a skill that makes agents write leaner code), and Graphy (which turns a codebase into a queryable knowledge graph to avoid grep back-and-forth). Treat "Inspect" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:34, where the video says: “by 60 to 90%. And the way how that works is whenever we have large function model here sending a bash commands right try to run a bash command or shell script for example get status let's say...”
02
Plan
Use "Plan" to locate the part of the codex + claude workflows workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 6:25, where the video says: “going to type in headroom. Okay? And we're just going to type in wrap and we're just going to wrap whatever AI agent you're using. If you're using codecs, if you're using Hermes agents, whatever it is, you...”
03
Edit
Turn "Edit" into the reusable artifact for this lesson: A routing matrix for when to use Codex, Claude, browser checks, or manual review. This is where watching becomes something you can inspect and reuse.
04
Verify
Use "Verify" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Review
Use "Review" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Route
Use "Route" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a routing matrix for when to use codex, claude, browser checks, or manual review..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video walks through four free repositories that cut Claude Code token usage on both input and output: RTK (a CLI proxy that trims bash command output), Headroom (a wrapper that compresses repetitive conversation history), Ponytail (a skill that makes agents write leaner code), and Graphy (which turns a codebase into a queryable knowledge graph to avoid grep back-and-forth).
02
Explain the practical stakes without hype: New playlist item from Eric Tech; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect -> Plan -> Edit -> Verify -> Review -> Route sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: 4 Free Repos That Cut Claude Code Token Usage
- URL: https://www.youtube.com/watch?v=g89FJiNAlEs
- Topic: Codex + Claude Workflows
- My current learning frame: Set up all four tools on one repo (RTK as a global hook, Headroom wrapping the session, Ponytail installed at project scope, and Graphy mapping the codebase), run a realistic multi-step task, and record the token savings each layer reports.
- Why this matters: New playlist item from Eric Tech; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:34 / Evidence 1: "by 60 to 90%. And the way how that works is whenever we have large function model here sending a bash commands right try to run a bash command or shell script for example get status let's say..."
- 2:29 / Evidence 2: "it. That that's how you can have this installed. So now if you want to start using your RDK and your AI agents, simply just type in your start your AI agent here like claude and we can..."
- 4:34 / Evidence 3: "cost for large model here to compile this. Well at this point you might be wondering okay how is it different compared to /compact from claw code. Well, like the description says, free up the context by summarizing..."
- 6:25 / Evidence 4: "going to type in headroom. Okay? And we're just going to type in wrap and we're just going to wrap whatever AI agent you're using. If you're using codecs, if you're using Hermes agents, whatever it is, you..."
- 8:26 / Evidence 5: "our large image model here. We also take a look at how to compress the entire conversation histories, right? By removing the repetitive information here from the conversations before we send it to a large range model. So..."
- 11:03 / Evidence 6: "before I show you the last skill, one thing that I want to talk about here is if you're looking to master AI agents, building automations and building real SAS products and I highly recommend to check out..."
- 14:06 / Evidence 7: "code. And lastly, we also take a look at how to actually improve our large model here for performance. Right? Whenever we've tried to have large model here defining information in our codebase or in our uh full..."
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
- 3 concrete examples that apply the video idea to real agentic work
- 2 failure modes the video helps prevent
- a checklist I can use the next time I run Codex or Claude
- one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "4 Free Repos That Cut Claude Code Token Usage", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a routing matrix for when to use codex, claude, browser checks, or manual review..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
What does RTK do to a bash command's output before it reaches the large model, and roughly how much does it claim to save?
How does Headroom differ from Claude Code's /compact command?
How do Ponytail and Graphy each reduce output-side token usage?
Source shelf
Use the video as a doorway, then verify with primary sources.
