§ 01 · The Hook
The bait, then the rug-pull.
Chase opens with the firehose problem every Claude Code user has — hundreds of new repos a day, almost none worth installing — then promises a curated ten. Almost every tool he covers shipped inside the last month, which is the real bait: this isn't a greatest-hits list, it's a now-list with an implicit expiration date.
What the video promised.
stated at 00:08“today, I'm gonna be highlighting 10 [tools] that are [worth your time]”delivered at 15:05
Where the time goes.
00:00 – 00:22
01 · Cold open + promise
Firehose problem stated, ten-tool promise made, freshness bar set to the last 30 days.
00:22 – 02:48
02 · Tool 1 — caveman (skill)
An Anthropic-style skill that makes Claude Code answer like a Neanderthal. Four levels (Lite / Caveman / Full / Ultra). Repo claims ~75% token savings; Chase recalibrates to ~5% in practice because thinking-tokens are untouched. Links the March 2026 arXiv paper 'Brevity Constraints Reverse Performance Hierarchies in Language Models' as the actual win — forced concision raises answer quality.
02:48 – 03:13
03 · Sponsor break (self) — Chase AI+ masterclass
Quick promo for his own Claude Code masterclass inside Chase AI+, updated weekly, framed for non-technical learners building an 'agentic OS.'
03:13 – 04:57
04 · Tool 2 — Graphify (knowledge graph)
Builds a real knowledge graph from your files. Claims 71.5x fewer tokens per query vs raw-file reads. Sits between Obsidian (just a markdown viewer with a pretty graph) and full graph-RAG systems like LightRAG. Multimodal — ingests PDFs, screenshots, diagrams, and videos via Whisper — but no embeddings.
04:57 – 06:37
05 · Tool 3 — claude-video (frame extraction)
Gives Claude the ability to 'watch' video. FFmpeg pulls frames at a duration-aware budget (30s = 30 frames, 10min+ = 100 frames cap), Whisper handles audio, both streams feed back to Claude Code. Alternative to round-tripping through NotebookLM or the Gemini API for video.
06:37 – 07:50
06 · Tool 4 — OpenDesign (Claude Design clone)
Open-source clone of Anthropic's Claude Design. Runs against any coding agent, free, fully local-capable. Built on four upstream tools (Huashu Design CLI, Gooszang PowerPoint skills, OpenCodeDesign, MultiCAD) plus 31 packaged skills. Pitched as the escape valve when you've hit your weekly Claude Design quota.
07:50 – 09:00
07 · Tool 5 — CodeBurn (token cost tracker)
Tracks token usage and cost across 16 different AI coding tools — way beyond what /usage shows in Claude Code. Breaks costs down by activity, project, model, core tool, shell command, MCP server. Critically, it doesn't just measure waste — it suggests optimizations.
09:00 – 10:00
08 · Tool 6 — Impeccable v3 (front-end skill pack)
One skill, 23 commands, all aimed at killing generic AI front-end output. v3 added a live mode — click components in a browser preview and cycle variations in place. The repo's website ships before/after pairs for every command, doubling as a design lookbook.
10:00 – 11:26
09 · Tool 7 — design-extract (any-site design tokens)
Companion to awesomedesign.md but for any URL. Headless browser scrapes layout system, responsiveness, interaction states, motion language, component anatomy, brand voice from a target site, then ships the bundle to Claude Code as a design foundation.
11:26 – 12:52
10 · Tool 8 — CareerOps (CLI job search)
Turns any AI coding CLI into a job-search command center. Playwright navigates job portals, parses descriptions, evaluates fit against your CV, tailors the resume per listing, generates PDFs, and updates a tracker. Explicitly framed as a scalpel — not a LinkedIn easy-apply spammer.
12:52 – 13:25
11 · Tool 9 — browser-harness (self-improving Playwright)
Playwright-style browser automation that rewrites its own skill files after every run. Per-site memory of what worked / what didn't, with a mini-Ralph-loop retry pattern. Just under 10k stars, only a few weeks old.
13:25 – 15:05
12 · Tool 10 — n8n MCP server (TypeScript-validated)
Anthropic's n8n MCP server. Difference from prior community attempts: it builds automations in TypeScript first, validates that the nodes wire together, then transpiles to JSON for the n8n instance. Closes the 'generated workflow won't import' bug. Released a few days before this video.
15:05 – 15:08
13 · Outro + CTA
Recap and second pitch for Chase AI+ masterclass.
Visual structure at a glance.
Named ideas worth stealing.
01:28concept
The Brevity Constraint
From the March 2026 arXiv paper 'Brevity Constraints Reverse Performance Hierarchies in Language Models': forcing a stronger model to be concise raises accuracy because it can't ramble itself into a wrong answer. Token savings are the side effect, not the prize.
Steal forAny prompt where the model loops or hedges into a wrong answer — add an explicit concision constraint and watch quality go up alongside cost going down.
01:00list
Caveman levels (Lite / Caveman / Full / Ultra)
- Lite
- Caveman
- Full
- Ultra
Four graded verbosity settings so you can tune how Neanderthal you want the agent to sound — Chase sits at Lite.
Steal forJoe's own skills — ship behavior with a dial, not a binary toggle. Lite is the default that gets people in the door.
03:35model
Graphify vs Obsidian vs LightRAG spectrum
Three tiers of personal-knowledge tooling on one axis: Obsidian (markdown viewer with a graph drawing), Graphify (real knowledge graph, no embeddings, layered on top of Obsidian), LightRAG / rag-anything (true graph-RAG with embeddings). Pick the rung that matches how serious your retrieval needs are.
Steal forWhen positioning a new tool, define the two neighbors it sits between — instant comprehension for the viewer.
05:26model
Frame budget by duration
Claude-video defaults: 30s video = 30 frames, 10min+ video = ~100 frames. Token cost is dominated by frames, so the budget scales sub-linearly with duration. Direct parallel to how mod-watch caps at 80 frames hybrid.
Steal forAny visual-ingestion pipeline — make the frame budget explicit, scale it sub-linearly with duration, document the formula publicly.
06:52list
OpenDesign's four upstream tools
- Huashu Design CLI
- Gooszang PowerPoint skills
- OpenCodeDesign
- MultiCAD
OpenDesign is a meta-package — one repo that stitches four existing open-source design-agent projects plus 31 skills into a single Claude Design experience.
Steal forIf a category has four mature niche tools and zero unifying UX, the win is the wrapper, not a from-scratch competitor.
12:56concept
Self-improving agent skill file (browser-harness pattern)
Per-task agent skill file that the agent itself rewrites after each run — capturing what worked, what didn't, what's already been tried. A mini Ralph-loop baked into a tool, not a meta-process.
Steal forAny agent that hits the same surface (a site, an API, a codebase) twice — let it write its own playbook after run #1.
13:56concept
TypeScript-first, JSON-last (n8n MCP pattern)
Instead of generating the deploy-target JSON directly, generate validated TypeScript, prove it compiles and the graph wires up, then transpile down. Validation lives in the source language, not in trial-and-error import failures.
Steal forAny agent that emits a config blob (n8n workflow, Trigger.dev task, Supabase migration) — make the agent write code that compiles to the config, not the config itself.
Lines you could clip.
00:56
“Why say many word when few do trick.”
01:45
“It doesn't change how it does its thinking. It doesn't change the amount of stuff it's ingesting. So overall, you're looking at about a 5% savings.”
02:14
“When we have powerful models and we force them to be concise, they're more likely to give us correct answers because they're essentially not going to talk their way into the wrong answer.”
03:40
“Obsidian, for all intents and purposes, is just a nice interface for us to be able to deal with markdown files.”
11:45
“This is much more of a scalpel that's going to tune your resume to the job — not just throw up all over the job application process.”
13:14
“Almost like a mini Ralph loop where we've given it a task. It's gonna always update its files to see, hey, did it work? Did it not work? What did we already try?”
How they spent the runtime.
Hook length22s
Info densityhigh
Filler6%
Sponsors
- 02:38–03:13 · Chase AI+ (self-promo for Claude Code Masterclass)
Things they pointed at.
01:49linkBrevity Constraints Reverse Performance Hierarchies in Language Models (arXiv, March 2026) ↗
06:52toolHuashu Design CLI
06:57toolGooszang PowerPoint skills
07:02toolOpenCodeDesign
07:05toolMultiCAD
11:26toolCareerOps
12:52toolbrowser-harness
13:35tooln8n MCP server
How they asked for the click.
15:05product
“Make sure to check out Chase AI plus if you wanna get your hands on that master class.”
Soft outro pitch back to Chase AI+ — same product he sponsored mid-roll at 2:48. Reinforces the CTA at the moment trust is highest, after delivering the promised ten tools.
Word for word.
HOOKopening / re-engagementCTAthe pitchmetaphoranalogy
00:00HOOKHundreds of new open source AI projects hit GitHub every single day, yet only the smallest fraction of a percent are actually worth your time. But today, I'm gonna be highlighting 10 that are. Almost every single tool we're gonna cover today has just come out within the last month. So unless you are as obsessed with this stuff as I am, I promise you're gonna get exposed to at least a few new tools. Now the first tool on the list is my favorite because it's one I use literally every single day at this point, and that is the caveman skill. This repo's gotten over 50,000 stars within its first month of release, and the whole idea is this just a skill that we can use inside of Claude code or codex that makes our agent talk like a caveman.
00:40AKA it's not gonna be so damn verbose. So you have some examples here where you have your normal Claude code response where it kinda just goes on and on and on. But if I use caveman, well, it's kinda just gonna get to the point. This repo has taken the idea of and just codified it. Now the cool thing about caveman is that there's levels to it. Like, . We can do caveman light, which is what I sit at. We can also do full or we can do ultra. Now I will say this repo
01:09gets a little excited when it comes about how much how many tokens you're saving. You'll say, like, hey. We're saving, like, 75% of output tokens. Understand that the way Caveman works is it's just going to be changing how many words you see. It doesn't change how it does its thinking. It doesn't change the amount of stuff it's ingesting. So overall,
01:26if we take it all together, you're looking at about a 5% or so savings when it comes to tokens. And I've done a full video on this, and I'll link that above if you wanna do a deep dive. Now I think the secret win when it comes to caveman, and I think they kinda bury the lead here, is the idea that our large language models might actually do better if they're forced to give more concise responses.
01:46CTAAnd this comes from a March 2026 paper. It's called Brevity Constraints, Reverse Performance Hierarchies and Language Models. And, basically, the long and short of it is when we have powerful models and we force them to be concise, they're more likely to give us correct answers because they're essentially not going to talk their way into the wrong answer. And it's actually a really interesting study, and I highly suggest you take a look at it. So we take those things together where we're going to be saving tokens and I'm potentially getting an actual quality increase. What's not to love about this thing? And it's just a simple skill. Installing this is super easy. You can just run the commands here inside the repo, or you can just copy the repo URL, put it inside of Cloud Code, and say, hey. Let's start running Caveman. And if you wanna do Caveman Lite, just say Caveman Lite. If you wanna do Ultra, do Ultra. It's very easy to execute. I'm always a huge fan of these lightweight tools that give us the wins on the margins without any real downside. So if you check out nothing else here, check out caveman. But before we move on to tool number two, a quick word from everybody's favorite sponsor,
02:44CTAme. So I recently came out with my Claude code masterclass, and it is the number one way to go from zero to AI dev, especially if you don't come from a technical background. I update this every single week, and we really focus on real life use cases and building upon the foundation of Cloud Code with things like an entire agentic OS system. So if that's something that you would be interested in, you can find it inside of Chase AI plus. There's a link to that in the pinned comment. Now tool number two is all about memory and knowledge graphs, that is Graphify.
03:15Now what Graphify is able to do is it reads our files to build a knowledge graph. And because we now give Cloud Code a clear structure to understand what we're working with, we're able to execute our task while using way less tokens per query. They quote 71.5 times fewer tokens per query versus reading raw files. Now when we talk about knowledge graphs and memory, a lot of us first start to think about things like Obsidian. But Obsidian, while this does give us a knowledge graph in theory and that's what we're looking at now, this isn't a true knowledge graph in the sense of, like, a graph rag system, something like LightRag or rag everything. Graphify is much closer to that true rag structure than something like Obsidian is. Remember, Obsidian, for all intents and purposes,
03:58is for us to be able to deal with markdown files and markdown files exclusively. Graphify is multimodal. Now it's not multimodal in the sense that it's gonna be ingesting pure video, something like, you know, Google's embedding too, but it is able to look at things like PDFs, screenshots,
04:16diagrams, and it's able to take videos and then use Whisper to pull what it needs out of there. Furthermore, Graphify doesn't use embedding. So when we're talking about sort of that spectrum between something like this, Obsidian, and a true rag system, something like LightRag, I would say Graphify sits somewhere in the middle. And it's something that we can essentially layer Obsidian on top of. So if you're someone who loves Obsidian, wants a little extra power in terms of what's going on with your memory and your files under the hood, yet you don't wanna take the step into some sort of true rag system with embeddings and everything like that, well, Graphify might be perfect for you. And definitely stay tuned for a deeper dive on this particular topic for on a video that might be coming out in the next few days. Now tool number three is one you probably haven't heard of before. It's Claude Video. Just came out last week. We're at 400 stars.
05:04And what it does is it gives Claude the ability to watch video. Now what do I mean by that? Because we know Sona and Opus can't ingest video. Well, this tool has a pretty clever approach. Once it's given a video, it uses FFmpeg to extract the frames at a particular rate depending on the length of the video. Obviously, if it was 60 FPS
05:24and it's a ten minute video, that would cost an insane amount of tokens. So it gives it a default frame budget based on the duration of the video. So a thirty second video would be 30 frames. If it's ten plus minutes, it would only be a 100 frames, so it gets kind of sparse. But it essentially feeds screenshots to Cloud Code, it grabs the audio via Whisper,
05:45and it uses those two things in combination to essentially watch videos. Now I think this is a really useful tool because when it comes to handling videos, there's really only two other pathways right now when it comes to something like Cloud Code or Codex. And that's, alright. Let's just send it off to something like Notebook LM and have it figured out. Or in kind of in that same category is, let's invoke
06:06Gemini via an API call and just send it that way. This gives us sort of a, you know, different approach where we aren't beholden to Gemini to deal with these videos for us because we're breaking it down via screenshots. Obviously, when we talk about longer videos, three minutes plus, ten minutes plus, you're gonna run into issues just like what are you actually trying to do with these videos.
06:27But I think anything that gets us closer to having Cloud Code being able to handle video is a great tool for us to play with moving forward. Now tool number four is one I did a video on recently and that is OpenDesign, which is essentially an open source clone of Claude Design. You can now use Claude Design or something pretty close to it with any sort of coding agent. So you could do this completely locally
06:49for free. You don't even have to be on Claude Code. They've copied the exact layout of Claude design in terms of being able to create prototypes, slide decks, and added some additional functionality like also being able to call APIs for image creation and for video creation. And OpenDesign itself is really built upon four other open source tools. The first one being Hua Shu design, which is basically another Clot of Clot design, but it's purely inside the terminal.
07:15The Goozang PowerPoint skills, so allowing us to create these PowerPoints and then actually extract them properly, as well as OpenCodeDesign and then MultiCAD. So it's taken all four of those, added a package of 31 skills, and voila, we essentially have local Claude design. So if you're someone who really likes claw design, especially the graphical user interface portion of it, I highly suggest checking this out if you've already hit your usage limits for the week. Now if you're someone who cares about where your tokens are going and how much money you're throwing away every single month on these coding tools, then you are gonna like tool number five, which is CodeBurn.
07:50CodeBurn tracks token usage cost and performance across 16 AI coding tools and allows us to get a much better look at where our tokens aka our money is going well beyond what, you know, forward slash usage is gonna give you inside of Cloud Code. You can see in this dashboard, it breaks it down by activity, project, model, core tool, shell commands, MCP servers, and shows us not only how many tokens we're using, but, like, the actual dollar amount, which is really important, especially if you're on the API. Now more importantly than just telling us where our tokens are going and how we're losing money, it gives us ways to fix the problems. It tells us how to optimize our systems so we stop burning so many tokens. So just like Caveman, think CodeBurn is one of those lightweight tools that is almost pure upside. So definitely take a look at this one. Tool number six is Impeccable. Now Impeccable came out a couple months ago, but they recently came out with their three point o version just last week, which is why I kinda wanted to include it because their updates to Impeccable include the ability to actually edit front end designs in a browser. And if you didn't understand by now, Impeccable
08:53is a tool for front end design. Impeccable ships with a single skill yet that single skill includes 23 different commands that are all about making sure your web pages don't suck. What I like about Impeccable is it includes this website where I can actually see what each and every command does. So it shows a before and an after. And you can see, okay, like, what will actually happen if I use this skill? Furthermore, it now has a live mode where you can actually bring up your web page, click on different components,
09:21and then go through different variations on the browser itself. I actually did a whole deep dive on this and I will link that video above if you wanna see this in action. But I think the best part arguably might just be the website and the ability to see all these before and afters and just kinda give you inspiration for like, alright. Here's what my AI slop looks like versus what it should look like and seeing the different ways you can make minor adjustments on individual components, but in totality, that can really change the way your website looks and feels. And again, this live mode just got released. So if you've used impeccable in the past without it, highly suggest you take a look at it again. So sticking with the front end design theme, tool number seven is design extract.
10:00Now a big repo that came out a little while ago, I've talked about in the past is awesomedesign.md. Now awesomedesign.md has taken off since it first came out about two months ago. It's up to 70,000 stars. And the idea is is they give us this repository of all these popular websites, say, for example, Eleven Labs. I click on it and I can see essentially an entire breakdown of what
10:24their website looks like from an aesthetic point of view. You know, what are the cards? What are the colors? What's the spacing? What's the font? Etcetera etcetera. The problem with Awesome Design MD is I can only choose from these. I mean, there's a lot to choose from, but I'm limited as to what I can do. DesignExtract takes it a little bit further because it's essentially allowing us to get the same thing I showed you here inside of DesignMD,
10:47but for any website we want. So we point this design tool at any website we wanna use as inspiration as a foundation for what we are building, and it's gonna grab the layout system, responsiveness, interaction states, motion language, component anatomy, brand voice, on and on and on and on. So we have a comprehensive thing we can then bring into Cloud Code and build upon with our brand. And it does all this by using a headless browser to actually grab all this information. So it's a bit more than just taking a couple screenshots
11:15and saying, hey. Copy this. If So you're someone who loves this awesome design repo but wishes there were some more websites on here that you could essentially use, well, definitely check out DesignExtract. If you've ever thought about using Claude code to help you apply to jobs or get your resume in order, well, you will like this tool, and that is CareerOps because that's exactly what it does. As they state here, CareerOps turns any AI coding CLI into a full job search command center. It evaluates the offers of the jobs out there. It generates tailored PDFs. It scans portals. It processes in batch and essentially tracks
11:49everything related to the job search process, which is brutal. And importantly, this isn't a tool that's just like a mass application tool. This isn't like, oh, go on LinkedIn and now apply to every single job under the sun. Like, this is that's going to tune your resume to the job and make sure the jobs you're actually looking at makes sense for you. This isn't just like, alright. Go out there and just like . Under the hood, it's using Playwright to actually navigate the pages. It evaluates the fit based on your CV and then adapts it per each listing. And here's how the general flow works. You paste in a job URL or description. It then classifies it. It then figures out, are you a match?
12:29Before then generating a report, the PDF, and then updating the tracker. So definitely a useful tool if you or anyone you know is trying to leverage something like Cloud Code to help them in their job search. Now Now tool number nine is one I think you're gonna hear a lot more about, and that is browser harness. So think of Playwright if Playwright was self improving after every single run. So the way it kinda works is if I used browser harness to say do something
12:53on Amazon, every time it went to complete a task on Amazon as this Autonomous Browser agent, it would update its own agent skill file saying, okay. This is what we did for Amazon. Here's what worked. Here it didn't. And almost in a sense, almost like a mini Ralph loop where we've given it a task. It's gonna always update its files to see, hey. Did it work? Did it not work? What did we already try? And then try again
13:16based on the information it wrote about itself and sort of the, like, self healing thing. So it's still pretty new. It's only been out for a couple weeks. It's just under 10 k stars. But I think this sort of agentic approach to these browser agents is something you're gonna see a lot more. Now I cheated on the last tool on the list because it isn't technically
13:35open source and even any then itself isn't technically open source. It's fair use, but, you know, you can use it locally so it gets a little confusing. And that is the any then MCP server. Now I think the death of any then has been greatly exaggerated, but let's be honest. It isn't in the same place it was even six months ago. Yet they've begun to realize and pivot into being a tool that Claude code can use very, very easily, especially with this brand new MCP server. So this MCP server is a little different than any other any in an MCP server that has come out because there's been a few out there, and they were open source. The difference is this one uses TypeScript instead of just trying to generate a JSON file automatically.
14:14So I give the N8N MCP some sort of command like build me whatever automation. It then builds it in TypeScript,
14:22CTAwhich allows it to actually validate the automation to see, hey. Do these notes make sense? Will this actually work? From there, as a last step, it gets changed to JSON, and then it populates inside your instance. So if you're someone like me who still really likes n eight n and there are use cases for it, although it can be kind of niche, this is an awesome tool. It just came out a few days ago, and I did a full video on that as well, and I'll link that above. So those are my 10 favorite open source tools for Cloud Code that have come out within the last month or so. Like I said, this space is literally always changing. It is impossible to keep up. So I hope by watching this, you were able to see at least a few of them that you might wanna check out. As always, let me know what you thought. Make sure to check out Chase AI plus if you wanna get your hands on that master class.
§ · For Joe
Steal the roundup format.
Chase AI playbook
A monthly 'ten tools that dropped in the last 30 days' video is the lowest-friction recurring format in the Claude Code creator economy — and Joe already has the audience for it.
- Pick a vertical you live inside daily (Claude Code agents, MCN+ stack pieces, video tooling) and commit to a monthly 'ten new things' cadence — freshness is the whole product.
- Each tool gets a 60-90 second segment: GitHub README on screen, one talking-head zoom, one hot take. Chase reuses the exact same shot for all ten — that's why he can ship 15 minutes in a week.
- Sandwich the sponsor (yours, not a brand's) between tools 1 and 2 while attention is highest. Chase puts Chase AI+ at 2:48 — that's the model.
- Bury a contrarian recalibration in each tool — Chase pushes back on caveman's 75% token claim with a real 5%. Pushback is the credibility currency for a roundup.
- Name the pattern explicitly when you spot one ('mini Ralph loop', 'scalpel vs spam') — those phrases are what gets quoted and shared.
- Keep the title in 'or fall behind' / 'or you're cooked' urgency framing for the first 90 days, then earn the right to drop it.
- For the $6 Stack: this is also a Mod Producer JSON runsheet — ten rows, one shot pattern per row, fifteen-minute batch record.
§ · For You
What this could mean for you.
If you live in Claude Code
Three of these ten ship today; the rest are watch-list. Don't try to install all ten — pick the gap in your stack and grab the one that fills it.
- Install caveman first — verbose Claude Code answers are a real productivity tax, the install is one paste, and downside is near-zero.
- Add CodeBurn next if you're on the API plan and don't know where your monthly spend goes — it's diagnostic, not invasive.
- Bookmark Graphify and re-evaluate in 30 days — knowledge-graph tooling is still pre-Obsidian-killer; don't migrate your notes yet.
- claude-video is most useful if you ingest podcasts or screen recordings — for native videos, NotebookLM is still smoother.
- Read the Brevity Constraints paper even if you skip every tool — the 'force concision to raise accuracy' finding generalizes to every system prompt you write.
- Skip design-extract until your front-end actually needs a system; it's a power tool for an already-painful problem, not a starter kit.
