Find Claude Code repos worth trying (Oct 2026)

Start with a topic list, not a search box, then run five checks on every repo you consider: license, last activity, forks, age and topics. On Oct 23, 2026 there are 81 repos behind our Claude Code repos page and 165 behind AI agents, and most are young enough that their star totals say little yet.

This guide is for a developer who already uses Claude Code and wants to pick hooks, skills or MCP servers without reading about 250 READMEs. It is a way to read the lists, not a list of recommendations.

How many Claude Code repos are there, and how new are they?

The Claude Code page holds 81 repos with the claude-code topic. Of those, 50 were created in 2026 and 26 in 2025, so 76 are under two years old. The other five were created in 2024 (2), 2023, 2022 and 2018 (one each).

The AI agents page is wider: 165 repos with the topics ai-agents, mcp or coding-agents. Among the 2,500 repos that have a page on the site, 100 carry ai-agents and 90 carry mcp, which tells you where the MCP server repos you’re looking for tend to sit.

Which Claude Code repos have the most stars?

The most starred repo on the topic is morluto/rea with 366,708 stars, created Apr 14, 2026. The rest of the top eight, all counted on Oct 23, 2026:

Look at the dates, not just the totals. morluto/rea reached 366,708 stars in the roughly six months between Apr 14 and Oct 23, 2026. Across all 2,500 pages, the fewest stars among repos created in 2026 is 18,572, so a 2026 repo appears on our pages only if it has 18,279 stars or more today.

What does a star total mean for a repo only months old?

It tells you that attention arrived, not that the tool works. A star is a bookmark, and nobody has to run the code to give one. On a repo created in April 2026, the whole total was collected in about six months, so there is no long record to lean on.

Age changes how you read the number. farion1231/cc-switch was created Aug 4, 2025 and has 147,717 stars. nextlevelbuilder/ui-ux-pro-max-skill was created Nov 30, 2025 and has 139,045. Two totals and two dates can’t tell you which one is moving now. Only a daily history can, and we explain the difference between the two measures in stars gained vs total stars.

What can you check on any repo in five minutes?

Run five checks, and drop the repo at the first one that fails. You can read each from the repo’s own page on GitHub.

1. License. Among the 2,500 repos with a page, 212 have no license. GitHub shows no license for those repos, so read the repo and ask the owner before you reuse its code. MIT (953 repos) and Apache-2.0 (489) are the two most common.
2. Last activity. Open the commit list. A hook that touches your shell or files should have been changed in recent weeks, not recent years.
3. Forks. Compare the fork count with the star count and open a few forks to see whether anyone changed the code.
4. Age. Compare the creation date with the star total, as above. Only one of the 81 Claude Code repos was created in 2018, so check whether that one matches what you need.
5. Topics. Topics are set by the owner. ui-ux-pro-max-skill lists claude-code next to codex and cursor-ai, among others, so a repo on the Claude Code page can name other tools too.

Then read the description and the README, and quote only what they say. For example, the data describes nextlevelbuilder/ui-ux-pro-max-skill as “An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.” and starts the description of farion1231/cc-switch with “A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent.” You can open both on their repo pages, ui-ux-pro-max-skill and cc-switch, and run the five checks yourself.

How do you tell a steady repo from a spike?

Use the 30-day star chart on each repo page: a steady repo climbs along a slope, a spike jumps in one or two days and then goes flat. On Oct 23, 2026 every chart has exactly one point, because we save one star count per repo per day (UTC) and collecting began today. The charts fill in over the following days.

When there are enough points, look at the shape first, then the size. We count stars gained as the latest snapshot minus the snapshot N days earlier, net of unstars, so it can be lower than the number of new stars. A flat line followed by a single large step on a young repo deserves a second look at the issues and the commits. How we rank describes the method in full.

When will there be numbers on who is rising?

The first weekly numbers arrive Oct 30, 2026, and the monthly ones on Nov 22. We aren’t naming any risers today because no stars-gained figure exists yet. When this week’s ranking is ready, the figures here get recounted, and the updated date at the top says when.

Can we tell if the stars were bought?

No. We don’t check for bought or farmed stars yet, so a big jump on a young repo is not proof of anything good or bad. Sponsors sit in a labeled card and never change a rank. Until we can flag suspicious jumps, the five checks above are your defense, and the one most worth doing is reading the code you are about to put in a hook.

Frequently asked questions

How do I find good Claude Code hooks, skills and MCP servers on GitHub?

Start from a topic list such as the Claude Code repos or the AI agents page, then run a five-point check on each repo: license, last activity, forks, age and topics. A star total alone tells you little about a repo that is only months old.

Does a high star count mean a Claude Code repo is good?

No. It means many people starred it, and on a repo created this year those stars were collected in months, not years. Read the license, the recent activity and the forks before you install anything.

Can RepoTrending tell if a repo’s stars were bought?

Not yet. We don’t check for bought or farmed stars, so treat a big spike on a young repo with care.

Where to look next

• Claude Code repos: the 81 repos behind the topic, most starred first today.
• AI agents: the 165 repos with the ai-agents, mcp and coding-agents topics.
• This week: the first weekly ranking, due Oct 30, 2026.
• Open source licenses on popular GitHub repos: the license check, counted for the 2,500 repos with a page.
• How to check a GitHub repo before you depend on it: five checks to run on any repo before you add it to a project.

Data used

More guides

• How to check a GitHub repo before you depend on it
• Stars per year: comparing old and new GitHub repos
• Daily, weekly or monthly: which window to watch?
• GitHub trending alternatives: what each one counts
• How does GitHub decide what is trending?
• Open source licenses on popular GitHub repos
• Stars gained vs total stars: which says more?
• Trending badge for your README, and what it says
• What 12,468 GitHub repos look like