Modern Creator
Nate Herk | AI Automation · YouTube

I Tried 100+ GitHub Repos for Claude. These 6 Are the Best

A talking-head rundown of ten Claude Code tools the creator uses daily, from scriptable video editing to security testing and SEO.

Posted
2 days ago
Duration
Format
Listicle
educational
Views
70.9K
1.7K likes
Big Idea

The argument in one line.

Out of 100,000+ Claude Code repos, a short list covering video editing, Google Workspace, scraping, website design, copy, planning, mobile, backend security, testing, and SEO covers an entire freelance AI-automation workflow.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…
  • A freelancer or agency builder using Claude Code to deliver sites, apps, or automations for paying clients.
  • Someone choosing between dozens of competing GitHub repos and skills who wants a tested shortlist instead of trying all of them.
  • A solo operator who wants to turn free open-source tools into billable services like content packages, website builds, or booking systems.
SKIP IF…
  • You're not using Claude Code or a similar coding agent for client work.
  • You're already deep into a specific toolchain and don't need a broad survey of options.
TL;DR

The full version, fast.

A creator who tested over 100 GitHub repos built for Claude narrows them to ten he actually uses: Hyperframes for scriptable video rendering, the Google Workspace CLI for Drive/Gmail/Calendar/Docs/Sheets access, Apify for scraping JavaScript-heavy sites, Scrollcraft for immersive website design, Humanizer for stripping AI tells from copy, Addy Osmani's Agent Skills for turning chat plans into resumable spec/plan/build files, Expo and Supabase/Stripe skills for shipping mobile apps and secure backends, Playwright CLI and Claude Security for testing and vulnerability scanning, and OpenSEO for keyword-backed optimization. He also flags three token-saving tools that under-deliver on their advertised savings. The actionable conclusion: install one tool that solves your current bottleneck rather than all ten at once, since the free repo isn't the product, what you build around it is.

Free for members

Chat with this breakdown — free.

Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.

Create a free account →
Chapters

Where the time goes.

00:00 – 00:24

01 · Finding the Best Claude Repos

Cold open: 100,000+ Claude repos exist and most are a waste of time; the creator tested 100+ and narrows to the ones he can't work without.

00:24 – 01:28

02 · Video Editing With Hyperframes

Hyperframes turns natural-language instructions into real rendered MP4 video (captions, title cards, reels), open source with no per-render fee.

01:28 – 03:09

03 · Google Workspace CLI and Apify

The Google Workspace CLI gives Claude Code CLI-level access to Drive/Gmail/Calendar/Docs/Sheets/Slides with 40+ built-in skills; Apify routes Claude around JS-walled sites via thousands of ready-made scrapers.

03:09 – 04:57

04 · Better Websites and Human Copy

Scrollcraft adds a real scroll engine plus codified design rules and a visual checker for immersive sites; Humanizer strips AI writing tells using Wikipedia's AI-detection guide.

04:57 – 06:20

05 · Planning Builds With Agent Skills

Addy Osmani's Agent Skills moves planning out of chat into resumable spec/plan/build files, surfacing edge cases like double bookings and refunds before a build starts.

06:20 – 07:34

06 · Expo, Supabase, and Stripe

Expo's official skills cover mobile app build/ship/App-Store rules; Supabase and Stripe's official skills enforce per-user data isolation and verified payment security.

07:34 – 08:32

07 · Browser Testing and Security

Playwright CLI clicks through the app like a real user and writes rerunnable tests without bloating context; Claude Security runs adversarial agent teams to find and verify vulnerabilities.

08:32 – 08:56

08 · SEO With Real Data

OpenSEO plugs Claude into real keyword, ranking, and backlink data for page-specific recommendations; free credits are small and data is hosted remotely by default.

08:56 – 09:46

09 · Token Savers and Usage Tracking

JetBrains-tested token savers (Caveman, RTK, Ponytail) under-deliver on advertised savings; CodeBurn surfaces wasted spend; CloudMem and ContextMode flagged as risky.

09:46 – 10:36

10 · Where to Start

Don't install everything at once; pick the one tool that fixes your current bottleneck, since the repo itself is free and the built product around it is what sells.

Atomic Insights

Lines worth screenshotting.

  • Hyperframes renders real MP4 video from Claude-written HTML and animations, with no per-render fee since the tool is open source.
  • The Google Workspace CLI reaches further than Claude's built-in desktop connector, which only works inside the desktop app and skips some surfaces entirely.
  • Apify connects Claude to thousands of pre-built scrapers, letting it read JavaScript-heavy sites like Instagram and Reddit that otherwise return an empty page.
  • Apify's free plan includes $5 of scraper credit a month before usage is billed per result.
  • Humanizer strips AI writing tells, like forced 'not X, but Y' setups and items stacked in groups of three, using the same guide Wikipedia editors use to catch AI-generated text.
  • Addy Osmani, a 14-year Google veteran now on Anthropic's Claude Code team, built Agent Skills to move planning out of the chat and into resumable spec/plan/build files.
  • A generated build spec surfaces edge cases, like double bookings or customers in different time zones, that a less experienced builder might not think to ask about.
  • Expo's skill repo encodes 20 signs that make an app look AI-built, plus current App Store submission rules, but has to be called by name since it doesn't always auto-load.
  • Installing only the narrow 'Stripe Best Practices' skill avoids the full Stripe plugin's habit of routing every vendor decision through Stripe.
  • Playwright CLI clicks through an app like a real user and writes rerunnable tests, without dumping full pages into Claude's context the way an MCP browser tool would.
  • Claude Security runs a team of agents that hunt for vulnerabilities and a separate team that tries to disprove each finding before reporting what survives.
  • JetBrains tested three Claude token-saving tools: Caveman cut 8.5% of output tokens against an advertised 65%, RTK saved nothing, and Ponytail saved about 10%, half its claim.
  • Ponytail, the one token-saving tool that measurably saved money, has an open Windows bug that can stall every message for several seconds.
  • The free GitHub repo isn't the product worth selling, since anyone can install it; the sellable thing is what gets built around it for a specific business.
Takeaway

Ten Claude Code tools that cover the whole client pipeline

WHAT TO LEARN

Each tool in this list solves one specific bottleneck in building and selling AI-automation work, from editing and research to planning, security, and proving things actually work.

02Video Editing With Hyperframes
  • Hyperframes builds real MP4 video from plain-language instructions by having Claude write HTML and animations, then render them, with no per-render fee since it's open source.
  • Layering purpose-built skills on top of a base tool (intros, reels, course videos, ads) turns one general repo into several sellable deliverables.
  • A simple recurring service, like 20 captioned clips a month for a gym, is a realistic way to monetize a free open-source tool.
03Google Workspace CLI and Apify
  • A command-line Google Workspace integration reaches further than the built-in Claude desktop connector, which only works inside the desktop app and doesn't cover every surface.
  • Over 40 pre-built skills ship with the Google Workspace CLI, so the agent already knows the correct way to touch Drive, Gmail, Calendar, Docs, Sheets, and Slides.
  • Apify routes Claude around JavaScript-walled sites like Instagram and Reddit by handing the request to one of thousands of ready-made scrapers instead of a raw page fetch.
  • Apify's free tier caps out at $5 of scraper credit a month, after which usage is billed per result.
04Better Websites and Human Copy
  • Scrollcraft pairs a real scroll engine with codified design rules (taste, depth, layering, spacing, typography) so Claude's output looks intentional instead of a generic fade-in template.
  • A built-in checker screenshots the rendered scroll positions so layout problems get caught and fixed before a human ever has to flag them.
  • Humanizer rewrites AI copy using the same guide Wikipedia editors use to spot AI-generated text, stripping tells like 'not X, but Y' setups, forced three-item lists, and over-the-top hype words.
  • Clean, human-sounding copy is positioned as an easier sell than AI-smelling copy, because readers lose trust and scroll past text that reads as generated.
05Planning Builds With Agent Skills
  • Long Claude Code sessions degrade because they get compacted or hit context rot, silently summarizing away earlier details.
  • Addy Osmani's Agent Skills moves planning out of the chat and into files with /spec, /plan, and /build, so a fresh session can resume exactly where the last one left off.
  • A generated spec surfaces edge cases a less experienced builder might not think to ask about, like double bookings, refunds, or customers in different time zones, before any code gets written.
  • Sharing the spec with a client before building creates alignment on scope up front, which heads off disputes about what was actually promised.
06Expo, Supabase, and Stripe
  • Expo's official skills encode both a list of 20 tells that make an app look AI-built and the current App Store submission rules, but Claude needs to be told to use them by name since they don't always load automatically.
  • Shipping to the App Store or TestFlight requires a $99/year Apple developer account regardless of how the app was built.
  • Installing only the narrow 'Stripe Best Practices' skill avoids the full Stripe plugin's tendency to route every vendor decision through Stripe.
  • Setting the Supabase connector to read-only and testing as a single logged-in user before launch is a fast way to confirm users can't see each other's data.
07Browser Testing and Security
  • Playwright CLI opens a real browser and clicks through the app like a customer, producing a rerunnable regression test instead of a one-time verbal claim that something works.
  • Because Playwright CLI is a command-line tool rather than an MCP connector, it doesn't dump full page contents into Claude's context, which keeps it lighter on tokens and faster.
  • Claude Security runs a team of agents that hunt for vulnerabilities and separate agents that try to disprove each other's findings, then returns a plain-English report of whatever survives.
08SEO With Real Data
  • An SEO tool that plugs Claude into real keyword, ranking, and backlink data produces page-and-keyword-specific recommendations instead of generic advice.
  • Free trial credits on this category of tool tend to be small, and by default the usage data lives on the provider's server unless it's self-hosted.
09Token Savers and Usage Tracking
  • Independent testing by JetBrains found Caveman cut about 8.5% of output tokens against an advertised 65%, and RTK saved nothing (and increased cost at low effort).
  • Ponytail was the only token-saving tool that actually saved money in JetBrains' tests, about 10% per task, which is still half its advertised claim, and it has an open Windows bug that can stall messages for several seconds.
  • A spend-tracking tool like CodeBurn can surface waste that's easy to miss, such as an MCP server that loads on every message but is rarely used.
  • Two previously recommended tools, CloudMem and ContextMode, are worth holding off on: CloudMem sends usage data by default, and ContextMode has an open bug that can burn through usage.
10Where to Start
  • Installing every tool at once makes it hard to tell which one caused a problem when something breaks, so pick the single tool that fixes the most pressing current bottleneck.
  • For a first install, the Google Workspace CLI, Apify, Scrollcraft, or Humanizer are reasonable starting points because they solve immediately visible problems.
  • The free repo itself isn't the product worth selling, since anyone can install it; the sellable thing is what gets built around it, like a cleaned-up site or automated workflow for a specific business.
Glossary

Terms worth knowing.

MCP server
A Model Context Protocol server that lets an AI agent like Claude call an external tool or data source, such as Apify's scraper marketplace, as part of a conversation.
Agent Skills
Instruction files that teach a coding agent like Claude Code how to perform a specific task correctly, loaded by name rather than running automatically.
Context rot
The gradual loss of earlier details in a long AI chat session as the conversation gets summarized or compacted to fit the model's context window.
Vibe coder
Someone building software by describing what they want in natural language to an AI coding assistant rather than writing code by hand.
Resources

Things they pointed at.

04:20toolHumanizer ↗
08:32toolOpenSEO ↗
09:04toolCaveman
09:12toolRTK
09:12toolPonytail
09:36toolCodeBurn
09:56toolCloudMem
09:56toolContextMode
Quotables

Lines you could clip.

00:01
“There are over 100,000 GitHub repos built for Claude right now, and honestly most of them are a waste of time.”
strong contrarian cold open→ TikTok hook↗ Tweet quote
09:58
“No one's going to pay you for a GitHub repo. Those are free, everyone can install them, so what you're selling is the thing that you build around it that solves their problem.”
clean closing thesis, no setup needed→ newsletter pull-quote↗ Tweet quote
09:13
“Caveman cut about eight and a half percent of output tokens where it was kind of advertising 65%.”
specific number debunking a marketing claim→ IG reel cold open↗ Tweet quote
The Script

Word for word.

Read-along

Don't just watch it. Burn it in.

See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.

So there are over 100 ,000 GitHub repos built for Claude right now, and most of them are honestly a waste of time. But after trying and actually using more than 100 repos, I found 10 that I cannot work without. Some of these help me finish projects 10 times faster, some save you money on tools you'd otherwise pay for every month, and some have completely replaced me in some parts of my workflow.
So in this video, I'll show you what they are, what problem each one solves, and how to use them to build something that businesses will actually pay you for. So let's not waste any time and just get straight into this one. Okay, so the first repo is Hyperframes, and this is from...
It's taken over a huge part of my video editing. You basically just tell Cloud what you want in natural language, and it builds the video out of HTML and animations, and HyperFrames renders a real MP4, so a real video, right on your computer. You can get captions, motion graphics, title cards, product promos, all that kind of stuff.
And then what I do is I build skills on top of HyperFrames to make things like YouTube video intros or Instagram reels, course videos, ads, so many things. Editing is no longer the bottleneck for me and my team. I'll literally drop in a raw clip and say, hey, can you add captions?
captions and a title card to this? Or can you turn this into an Instagram reel? And a few minutes later, I've got a finished file.
Now you might've heard of something like Remotion, which also does this, but I've just found way more success with Hyperframes. It's not a sponsored video at all. And I've enjoyed the experience using Hyperframes a lot.
It's open source. It has no per render fees. So It's completely free.
And pretty much any business that post videos will pay for you to edit videos for them. Like a gym that wants 20 caption clips a month or something like that. You can sell that as a monthly content package.
And you don't have to have any video editing experience to actually use these tools. Okay, so number two is one of the things that I use the most. And it's the Google Workspace CLI.
It lets cloud work with pretty much anything in your Google account, like your drive, Gmail, calendar, docs, sheets, and slides. And it formats everything beautifully using the CLI. Now you could obviously use the built -in connector.
for Google inside of Claude, but those only work inside of the Claude desktop app. They don't cover everything. But this is a CLI, a command line tool.
So Claude code. codex or any other agent that you build with can use the cli and it comes with over 40 skills so cloud already knows exactly how to use it now setting this up will just take a few minutes because you do need a google cloud project for the login but then cloud can just walk you through it step by step you just have to give access to the apps that you actually want to use through the cli and most small businesses run on google so weekly reports invoices follow -up emails anything like that you can help them automate that quicker all right repo number three is appify or it's technically the appify mcp server there's a ton of data out there that Claude just cannot naturally or natively, I should have said, reach and touch.
Sites like Instagram and Reddit, they might either block it or just need JavaScript to load it. So Claude basically gets back an empty page. So Abify connects Claude to thousands of ready -made scrapers for Instagram, TikTok, Amazon, tons of different websites.
So I'll basically just ask it, hey, can you find bakeries in Chicago on Instagram and give me their follower count and download the videos and show me the ones with no websites in their bio, things like that. And then a couple of minutes later. You've got a spreadsheet right there.
The connector is open source, but the scrapers run on Apple Fi's cloud. So you might have to pay a few bucks depending on which scraper you're using. The free plan gives you...
five bucks of credit a month. And then the other actors you might have to pay for, like I said, per result. There are also some other open source repos out there that help you scrape different things like Firecrawl, but Appify has been really easy to use as well.
All right, so full disclosure, this next one I built and it's called Scrollcraft and I'll link it in the description. You've probably seen those Apple style websites where you scroll and the whole page moves like a movie and it's super immersive. There's different layers.
It just feels cool. And if you ask Claude for one, you usually get a very generic page with a couple of different weird text fade -ins or something like that. So Scrollcraft, gives Claude a real scroll engine, plus the design rules that I've picked up by building a bunch of different websites, and it has a checker built in that screenshots the scrolls and looks at the positions so Claude can fix things before you ever have to instruct it to fix those things.
My AI Automation Society site, my personal site, our event sites, every site that we build uses this repo. And what you'll notice is that not all of these sites have to be super, super scroll -driven and immersive. The repo understands things like taste and depth and layering, spacing, typography, color schemes.
understands just tons of great stuff for website design and for feel. Because ultimately the point of a website is to feel good and to be able to actually convert the user to do what you want them to do. Nowadays with AI, a basic landing page is pretty much a commodity, but brands that sell online still pay a designer real money for, you know, a custom scroll experience or something that's not as easy to vibe code.
So trust me, this repo is going to come in handy when you're building your next site. Okay, now repo number five. This is something that I found almost by accident and it's been on every project since.
It's called Humanizer and it makes whatever Claude writes, stop sounding like AI slop. It's built on a guide that Wikipedia editors use to catch AI generated text.
So it knows all of those like AI tells when you can just immediately look at it and it smells like AI. Things like not this, but that. All of those sort of setups or tee ups.
Everything coming in groups of three. Over the top hype words. You basically just have to paste in website copy or the cold email that you're about to send or whatever it is.
And you just tell it to humanize it using this repo. And it keeps what you were saying, but it drops the stuff that makes people instantly scroll past. lose trust.
Because obviously, a copy that reads like a person wrote it is a way easier pitch than AI generated content. Okay, so those first five were really about landing a client.
The rest of these here are more so about when a client asks you to build something real, like a cleaning company that wants customers to book online and pay a deposit. And you've probably had this happen where you're maybe an hour or two into a build and cloud starts randomly giving you answers like it forgot everything.
And that's because long sessions get compacted or you maybe enter context rot and details from earlier get summarized away. So repo six fixes that. It's called agent skills from Addy Osmani.
Addy spent 14 years at Google and now works on cloud code at Anthrop. So it gets the plan out of the chat and into files. You can run slash spec and it writes a real spec with you.
You can run slash plan, which breaks it into small tasks. And then you can run slash build, which works through them one at a time with a check on each one. So when a session inevitably gets messy, you can just open up a fresh one and it can pick up right where you left off.
The spec will also ask about things that you probably wouldn't think to bring up, like double bookings or refunds or customers in a different time zone. All of these edge cases that's really important to bake into your actual spec or your build. And it's something you can hand.
client before you build anything so they know exactly what they're actually getting. That way you guys stay aligned all the way through. And if you've been using something like Superpowers from my skills video back in May of this year, Superpowers is still really good, but Addies is easier to follow if you're newer.
And there's also other skills like Matt Pococks, which are really, really good, especially if you're wanting to build like a developer, even if you're not a developer. So I guess Matt Pococks would be a bonus GitHub repo inside of this one right here. But let's move on to number seven, which is Expo's official skills for mobile apps.
You can basically go from an idea to a real app running on your own. iphone in an afternoon even if you're on windows and they include expo's own list of 20 things that make an app look ai built plus the current rules for getting into the actual app store so one quick tip tell claude to use the expo skills by name because they don't always load on their own you will also need a 99 a year apple developer account for test flight or the app store and most shops already have something like square so sell them the one workflow their current software doesn't fit but trust me if you guys want to get an app into the store and you want to build it in a way that actually makes sense this repo is going to save you a ton of time and tons of headaches.
Okay, now number eight is on the back end of that app that you're building or software that you're building with Supabase and Stripe's official skills. So if your app needs logins or a database or payments, which pretty much every app does need, Cloud knows each company's actual security rules, like making sure users only see their own data and checking that a payment really came from Stripe.
So only install Stripe's skill called Stripe Best Practices. You don't need the whole plugin to start because the full plugin might try to route every vendor decision through Stripe. And then you can set the Supabase connector to read only and then log in as one test user before you launch and make sure you can't see other users data but trust me i know that the back end and the payment stuff can get very confusing if you're vibe coder you might get worried about some security stuff so use these skills now number nine is what you run before you hand anything over to a client or to the internet because cloud will happily tell you yeah this works but it might not have actually clicked those buttons and checked if it really did work so playwright cli from microsoft opens a real browser it clicks through your app like a customer would and it writes test that you can rerun.
over and over and basically just verify everything. And since it's a command line tool instead of an MCP, it doesn't dump the whole page into Claude's context. So it's a lot lighter on tokens as well.
And it's a lot faster, honestly. So this helps you verify and test a ton of things and find those edge cases. And then we also have Claude Security, which is Anthropic's security plugin.
It sends a team of agents through your code looking for holes and separate agents try to prove each other wrong. And they try to look for different findings. And you basically get a plain English report of everything that survived.
And then it can write all those patches and just execute. on it for you. Now, clients don't usually care about all these tests, but what they really care about is that the booking form works and that their customer data doesn't leak.
So build this into every project. And last but not least, we have number 10, open SEO, because once the site or app is live, people have to find it. It plugs Claude into real keyword data, rankings, backlinks.
So instead of generic advice, it tells you the exact page and the exact keyword where you're sitting at. Agencies use an audit like this to win the month the SEO retainer. So just know the free trial credits are small and by default, your data sits on their server unless you host it yourself.
Now some of you guys might be wondering about some of the token saving repos like Caveman or RTK, Ponytail, things like that. Now JetBrains actually tested all three on real coding tasks. Caveman cut about eight and a half percent of output tokens where it was kind of advertising 65 % and RTK didn't really save anything and at low effort it made tasks more expensive.
Ponytail was the only one that saved money in these tests about 10 % per task which is half of what it advertises and on Windows it has an open bug that can stall every message for several seconds. So if you want to see where your tokens actually go, a repo called CodeBurn shows your spend and flags the waste like an MCP server that you might never use, but still loads on every message.
And two I recommended back in May, CloudMem and ContextMode. I'd maybe hold off on those for now. CloudMem sends usage data by default and ContextMode has an open bug that can burn through your usage.
So everything else I tested and left out will be in the description. All right, so if you're brand new to this, don't install all of these today. I think that would be extremely overwhelming because if something breaks, you might not know.
which repo caused it so just pick the one that fixes the problem that you're currently kind of running into the most and if you're not sure then maybe start with the google cli or appify or scrollcraft and you might as well start with humanizer because that one is super super simple as well but pull a list of businesses with no website you know build one off a sample page clean up the copy and then send the link no one's going to pay you for a github repo those are free everyone can install them so what you're selling is the thing that you build around it that solves their problem and i'll put every repo from this video inside the description of the video so that you can just go ahead and click on all of them right from there.
But anyways, that is going to do it for this one. So if you guys enjoyed or you learned something new, please give it a like. It helps me out a ton.
And as always, I appreciate you guys making it to the end of the video. I'll see you on the next one. Thanks, everyone.
The Hook

The bait, then the rug-pull.

The published title promises six repos, but the video itself opens with "these 10 that I cannot work without" and counts all the way to ten on screen. The actual list runs from scriptable video rendering to backend security and SEO, each tool solving one specific bottleneck in freelance AI-automation work.

CTA Breakdown

How they asked for the click.

VERBAL ASK
10:30subscribe
“So if you guys enjoyed or you learned something new, please give it a like. It helps me out a ton.”

A single soft engagement ask in the last few seconds, no in-video pitch for a paid product despite the description carrying monetized links to the creator's Skool communities and a Scrollcraft opt-in funnel.

Storyboard

Visual structure at a glance.

open
hookopen00:19
repo 1
valuerepo 101:15
repo 7
valuerepo 706:57
close
ctaclose10:27
Frame Gallery

Visual moments.

One-click upgrade to your Google

Get more breakdowns in your search results

Add Modern Creator as a preferred source and Google shows you more of our breakdowns in Search, Top Stories, and AI Overviews. It only changes what you see, and you can undo it in your Google settings anytime.

Add to Preferred SourcesOpens your Google source preferences with us pre-loaded. Tick the box and you're done.
Watch next

More from this channel + related breakdowns.