Cut LLM cost by 95%, replace ElevenLabs, and 10 top GitHub repos

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: Cut LLM cost by 95%, replace ElevenLabs, and 10 top GitHub repos
- URL: https://www.youtube.com/watch?v=n8rP6Ceskm4
- Topic: Agent Architecture
- My current learning frame: Use low-cost AI repo scouting as a transcript-backed agent architecture walkthrough: at 1:18, it frames unfortunately not.
- Why this matters: New playlist item from The Next New Thing; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:18 / Evidence 1: "unfortunately not. >> Um no, I mean, in terms of the overall project, it's actually quite well structured and it does what it says it's going to do. Um, but the problem is, do people want to watch..."
- 7:14 / Evidence 2: "me and why I think we've been doing really well. Peter, my problem is that I keep moving from like Claude to Codeex to this to that. And I want to bring all of my tools along with..."
- 11:51 / Evidence 3: "Again, honorable mention heard on X. Uh, this is Gary Tan building a permanent memory for his AI agents. Then he gave it away. Uh, and he's been adding more and more features to it. I think this..."
- 17:32 / Evidence 4: "well. This is largely a giant set of skills which tell you all kind of instruct claude and codecs and the way they've coded it is actually kind of cool because it actually plugs into almost any of..."
- 23:56 / Evidence 5: "next one. Um, ECC. This is a builder who spent 10 plus months living in AI coding tools, packaged everything he learned into 63 specialized agents, 249 skills into one free install. It's the closest thing to an..."
- 28:00 / Evidence 6: "files brought into a project. >> And the reason for that is that because it's about taste rather than how to do things. >> And so I don't mind other people's opinions necessarily being brought into design if..."
- 30:30 / Evidence 7: "there is a lot to reading large code projects that you can't just go to, you know, codeex or claude and say, I'll read this project and tell me x, y, and z. Sometimes there is a lot..."

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 one-page agent harness map with tool boundaries and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Model -> Harness -> Tools -> Verifier -> Artifact
   - 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 "Cut LLM cost by 95%, replace ElevenLabs, and 10 top GitHub repos", not a generic Agent Architecture 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.