10 Github Repos That Solve Your Token Problems

0:00The first repo you've got to know about is something that addresses a problem we all have. Maybe we have like a flip switch that we want to turn green or a button that when we hover over it changes colors and moves. How do you describe them to your agent so that it could build it? Well, that is where screenshot to code comes in. You just screencast what's on your screen and then you give it to it and you end up with clean code. This thing has been incredibly popular, 74,000 stars and I

0:26can see how useful it is. Take a screenshot, drop it in and you're off to the races. Next, you have a website and maybe that's what this tumbleweed is about that nobody shows up or maybe you do have somebody who comes on the site and they're just rage clicking the enter button because it's not working and they're getting so frustrated that they never want to come back to your site again or even see anything else you

0:44build. How do you know what's going on? Well, that's where PostHog comes in and they've got analytics, session replay so you can see what's going on, error tracking, feature flags, all these things in one place and best better yet, it's made in a way that you can give to your agent. It has got 37,000 stars. I thought it was a paid product though, Tim. What's the deal with them giving it

1:05away here like this? On GitHub. Yeah, it's open source but like you can actually use you can just go through the PostHog install wizard and they give it away. They have a very generous free tier. And one of the things that I really like about this after having gone through the install wizard on a couple of my own, um you have can actually stitch your marketing website directly to your your in-app product um and get those get those rich analytics and they just give it away. Um until you obviously hit your event limit and then then you have to you have to start paying but very very generous and super

1:36easy to install. Okay. Love this one. Of course, we'll have links to this and this whole report um below in the comments and in the description. Next, half the apps you use shipped with a connector to ChatGPT haven't shipped with a connector. Is it half? It's even more. A lot of the apps when I try to work with Claude on them, Claude doesn't have a connection to it and so what you have here is Zapier, which has a set of connections that I thought you all charge for, but I see that it's on

2:03GitHub. What's the deal here? Yeah, that's so there's This is actually pretty It's near and dear to my heart. So, like one of the one of the key things about the connectors repo is that we're actually starting to expose all of the integrations that we have in just good old fashioned coding language. So, that way you can actually use the connections and the integrations that we've built over the years, and you can either log in with the app credentials that you have, or if you're a Zapier customer, you can authenticate with your with your Zapier account. The beauty of this is that we just want you

2:33to get started. So, that way if there's a connector that's missing, go check out the the Zapier connectors repo, grab that. You can use it in MCP, you can use it in your SDK. It really doesn't matter, and then you can bring your own auth, or you can use Zapier to authenticate, and you'll just be off to the races.

2:48This one's really fun. if I want to connect into SharePoint or Microsoft To Do or Notion or any of these, and they happen not to have a connect connector, I could come in and use this completely for free. Don't even have to pay Zapier. That's correct. I don't know how you're doing it. I don't know why you're doing it, but I'm glad it's there. If you like it, hit the

3:06star on it, show them appreciation. Let's go on to the next one. All right. You have a great idea to build something. So, you sit down in front of your agent, and you tell it to start building. And maybe that first version looks good, and you're excited. But then, for the next 2 hours, you're fixing your agent's mistakes, you're getting frustrated by how slow things are, and you're wondering, why is it that this seems so much easier for

3:24everyone else? Well, Matt Pocock, the developer teacher, has got your back. What he did was he said, "Look, developers who are operating well have a structure for how they do things. They don't just sit down and start to create. They think. They get They ask questions. They go through a process." And he said, "You know what I'm going to do? I'm going to take the process that I use myself as a developer, and I'm going to make them available for people." And that's what this repo is. I have got to tell you

3:50this thing is taking off. 221,000 stars. It is one of the top 20 repos of all time on GitHub. He and I just did a whole session on this where he showed it to me. It's incredible. Thoughts on this one? I love it because he's basically made these super composable and they're small. So, they don't get in the way of the actual engineer when they're developing using these coding agents. If

4:10anything, they're kind of supplemental. You have full control over them. This one's super helpful. If anything, it kind of feels a little bit simple. When you click into one of the skills, it's short, it's clear. You see exactly what's going on. You're not meant to use it blindly, you're meant to understand it and then you can use it.

4:25All right. You give your agent a task. Yes, here's number five on the list. You give your agent a task, then you sit back and you watch it work. It runs a command and the screen fills with output. Then it runs another and then another screen full of output. It's all this I start to blank on it and I don't read any of it. That's why you told me, Tim, about the fifth

4:42repo that we're locking about today. It's RTX. It sits between your agent and your computer. It squeezes out all that output before your agent before you get to it and before your agent reads to it. I'm actually, to be honest with you, not as clear about this as I should be. Teach me, what is this? It just reduces cognitive load. So, it's actually not going to like your eyes

5:02aren't going to track on all of this. It's going to actually go ahead and jump ahead of the line and it's going to squish all of this stuff and compact it nice and neatly so that way you're not sitting there watching all of this happen. It's going to It's going to save you some some brain power. here, this run, this CSE, the whole

5:17thing in this bash. It's compressing. That's right. Yeah, exactly. So, that way your eyes aren't tracking on that the whole entire time you're building these things. It's It's actually quite nice. I've heard people talk about it as a way of saving tokens and you said, "Andrew, that's not really what it's about. You might save a couple, but It does reduce some tokens, but it's not like it's not like this big like token saving secret. It's It's really It does reduce the amount of it to some extent, but really what it's doing is it's saving your the the most valuable resource, which is like your your cognitive load and your and your brain

5:45power. Like you don't want to get fatigued. 76,000 stars on GitHub, incredibly popular. All right, thanks. Let's go on to number six. Your agent doesn't know your project. So, before it could change anything, it starts to go hunting. It opens a file, then another. It looks for something and where it lives and pretty soon you sit there and you go, "You know what? I could have answered that question in 5

6:05seconds." In comes GraphiPy. That's where it's helpful. It maps your whole project, the code, the docs, the PDFs, even images, all in one picture of how everything connects and it makes it easier then for your agent to understand without having to dig through your files. It's got over 100,000 stars. I keep seeing it as one

6:24of the top repos of the week. Do you have any opinion on this one? Andrew, I am a knowledge graph fanboy. Tell me. And and they they they're giving it away here, right? Like, obviously you can you can go you can level up, but this is pretty cool because once you have a knowledge graph, you can see the relationships between all of the things

6:43and it just makes things make sense. It's incredible. All right. Number seven. You got Claude code working, it's running, everything's good, but you keep getting the feeling that everyone else is doing so much more than you are with it. They've got skills, they've got plugins, they're talking about workflows that you never heard of. Meanwhile, you just don't know

7:01where and what to where to grab these. Well, it turns out there is a repo, it's called awesome Claude code. It is got a hugely not just large, but a curated collection of skills, of plugins, of tools. I put some of them over here. The issue I've got with this, and I've heard about how good this is, Tim. It is fantastic, but I don't even have the time to read through all of it, let alone to know that this one is going to be useful for me, but this one is not. What do I do with all these? And I'll open it up in GitHub while you're at

7:28Andrew, that's the That's the beauty of of GitHub repos like this is that you actually don't have to spend the time parsing through the repos. You can simply just have your agent do it for you. How? So, that way if you wanted to get up to speed quickly, you could say, "Hey, I'm new to Claude code. I really want to use this repository to set myself up for success." And it'll walk you through all

7:47of the things that you might need to do. It'll ask you questions about like, "Hey, what are you trying to build today? What are the most common tasks that you have?" And then it will go through that repository and it'll actually tell you the things that you need to either enable or add as skills or set up from an environment

8:02perspective. I see. Okay, I just give it this. It interviews me and knows based on what I'm doing which of these tools will help me do a better job. This I can see our audience for sure using. Next. Oh, and by the way, 52,000 stars and it's been incredibly popular. I've seen it a lot. I'm I'm kind of a little jealous, by the way, of people who have

8:21these awesome skill collections. Everyone talks about them. Everyone contributes. They get all kinds of attention. So many people are being helped by it and all they're doing is curating and I I love it, but I'm a little jealous, to be honest with you. I need something like that. Same. All right. Number eight for today. In the past, we used to go to Google to search, but people right now are going to chat GPT, to Gemini, to Claude and we're basically starting to ask questions like, "I need

8:47a bookkeeping company. I need a lawyer." And that's where they're getting their list of answers. Well, how do you get cited by it? When it came to a search engine optimization, a lot of us had heard a lot about it. A lot of us had learned about it, started using it. But when it comes to AEO, answer engine optimization, we're kind of newbies and that's where this comes in. It's awesome AEO and SEO and it's basically collecting the research on how

9:11AI search actually decides what to cite. I wasn't sure if you gave me the wrong repo, Tim, when you told me that we should include this one because when I looked at it, it had two stars. Did you mean to give me this? it's a I did. Little sus, right? Um the reason why I like this is cuz I've I've got years and years of experience doing SEO and essentially, nowadays, what you have to do is just understand how these engines

9:35work. Right? And with engine answer optim- or or answer engine optimization and search engine optimization, a lot of that stuff is out there in the wild. With the beauty of it though is that this this gentleman put this package together and it's actually really well done. Um there's a lot of information here that's following the new standards. It's actually pulling research that's been been curated over the over the past year or so. Um and it's relatively like right on the nose. So I just wanted to put this one in here because it's it's wor- it's notable. Right? Like you should probably try this one out, use it, and

10:08it'll definitely help you out. All right. I'm going to hit the star on this one. Give it three stars and let's go on. And by the way, speaking of stars, if you do like this, you can't give me a star on YouTube, but do subscribe, give me a thumbs up, and obviously, not obviously, complain. Even

10:21if you don't like it, I want to hear it. Let me know in the comments, especially if you don't like it. I want to know. I've been adjusting and speeding up. You can see me constantly tweaking based on your feedback. So subscribe, like, but also let me know what else we can do to make this more useful for you. Number

10:34nine. All right. Your agent writes code fast. Fast enough that at some point you stop reading all of it. Then a few weeks later you've got a code base full of patterns nobody chose, error handling that isn't there, decisions that nobody remembers making. Essentially, slop slop slop slop all the way down. That's where Vibe Coding Playbook comes in. It treats your agent like a junior engineer. One that has to propose a plan before it writes anything, follow patterns you already use, and pass a review every single time. You keep the speed, but you

11:03skip the big mess. Why did you pick this one to for us to include? I like this one because it really does do that. It kind of like forces you to slow down as kind of like a if you're if you're new to this game, it's actually going to structure your your code base the right way. It's going to ask you the right questions and it's going to make you approve things before you just

11:23like push it all out there. Right? Makes it nice and organized, helps you get through it a little bit easier, keeps things clean. That's why I I it. A lot less slop. Only 311 stars now, 312. One of the things that I learned by talking to you and other people who are further ahead than me is, Andrew, slow it down. Ask the right questions first, figure out what you really want, and then you won't have these problems that you have later on. All right, I

11:47appreciate it. Let's go on to number 10. You build something good, you put it on GitHub, then someone asks you how to use it, so you start writing a read me, then another page, then you need a sidebar for a site that you've created with all the documentation and a search bar and somewhere that you're going to put your version history and pretty soon you're no longer just focused on the thing that you put on GitHub or the project that you made, you're now building a whole website and setting telling the thing

12:09what to build. And that's where Docusaurus from Facebook comes in. It will create these beautiful pages that we've seen. I'm actually here in the right. I picked out actual sites that were built using it. Why did you pick this? I love Docusaurus cuz I'm I'm kind of like a a technical doc fanboy. You are?

12:31As a As a knowledge graph fan I am. Because that's as as a developer, like that's where you want to spend a lot of your time like really understanding how to use the technology, right? And what Docusaurus does is going to take all of the information that you've written in your inside of your repository and it's going to help you create those tech docs. So like whenever you go to a docs.zapier.com or a docs.gitlab.com, like you're going to find the information that you need and it's going to be structured in a way that's easy to easy to read and also understand. The beauty of this is that it's creating it

13:01in markdown files automatically. So that way it's easy for agents to actually consume, it spends less tokens, and then it informs the agent what to do. Docusaurus handles all that stuff for you. It's incredible. It's a good one. You all over at Zapier have been so far ahead of everyone in making content that is accessible to agents and now I can

13:20see why you're excited about this. 66,000 stars. All right, we've had a big list here. If you got anything of value, you should know that every week I break down the top 10 trending GitHub repos of the week right here on the channel. When you subscribe, you'll find out about it. And I've got my email address on the channel. It really is me. And if I get overwhelmed, someone on my team will help me. But we are trying to figure out

13:40what you're building. I want to see it. Send me over what you've built. A lot of people will take these and then fork them and create their own versions. I want to see it. And if there's anything else that you're building and creating, I want to see that, too. Speaking of our weekly GitHub show, I've got one right here that I think you're going to like if you got this far. I'll see you in

13:56that one.