10 Open-Source Claude Code GitHub Repos Worth Cloning in 2026 (Frameworks, Skills & Workflows)

Cloning a good repo beats reading ten tutorials. The Claude Code ecosystem on GitHub got genuinely big in 2026, and the highest-value repos aren't demos — they're frameworks and skill libraries that encode real engineering discipline you can drop into your own projects.

This is the clone-and-learn list. For the bigger picture on how to structure a project, see the Claude Code projects hub; for what to build, the 15 project ideas; to get set up, the beginner tutorial.

A note on the numbers: every star count below was checked against the live GitHub API on 22 June 2026. Stars move — treat them as a signal of adoption, not a precise figure.

The repos, at a glance

Repo	Stars (Jun 2026)	What it gives you
anthropics/claude-code	~134k	The official tool — the foundation
obra/superpowers	~236k	TDD + subagent methodology, guardrails
mattpocock/skills	~141k	Production engineering skills
garrytan/gstack	~113k	A role-based AI engineering team
ComposioHQ/awesome-claude-skills	~66k	1,000+ skills + SaaS integrations
hesreallyhim/awesome-claude-code	~47k	Curated patterns, hooks, commands
yamadashy/repomix	~26k	Pack a codebase into AI context
mukul975/Anthropic-Cybersecurity-Skills	~18k	Security skills (vertical)

The official core — study the foundation

anthropics/claude-code (~134k★, Python) — the reference implementation. You don't fork this to build on it, you read it to understand the category: how a terminal-native agent understands a codebase, plans multi-step work, handles git, and exposes plugins, skills, and MCP. Start here for the mental model, then layer the community tooling below.

Agentic frameworks — the highest clone value

These encode how to work, which is the part that actually decides whether your output is reliable.

obra/superpowers (~236k★, Shell) — the most complete agentic methodology out there. Enforced test-driven development (red-green-refactor), subagent-driven development, mandatory planning and review stages, git worktrees, and cross-agent plugins. It's the strongest set of guardrails against vibe-coding drift — clone it if you want discipline baked in rather than hoped for.

mattpocock/skills (~141k★, Shell) — production engineering skills from Matt Pocock (Total TypeScript), described as tools "I use every day to do real engineering — not vibe coding." Concrete, composable skills: /tdd, /diagnosing-bugs (reproduce → minimize → hypothesize → instrument → fix), /improve-codebase-architecture, /to-prd and /to-issues, plus /handoff for agent-to-agent summaries. Small and adopt-one-at-a-time — the easiest serious upgrade.

garrytan/gstack (~113k★, TypeScript) — from Garry Tan (YC). Turns Claude Code into a virtual engineering team: 23 role-based slash-command skills (CEO planner, designer, eng manager, QA with real browser/iOS testing, release manager) over a Think → Plan → Build → Review → Test → Ship → Reflect workflow, plus power tools and domain skills. Built for founders who still want to ship, and for first-timers who want structure instead of a blank prompt. MIT.

Skill libraries & discovery hubs

ComposioHQ/awesome-claude-skills (~66k★) — a library of 1,000+ production-ready skills across document processing, dev tools, data, business, security, and creative work, plus 78 Composio-powered SaaS automation skills (HubSpot, Salesforce, Jira, Slack, and more). The canonical place to find a skill before you write one.

hesreallyhim/awesome-claude-code (~47k★) — a hand-curated index of high-quality skills, hooks, slash commands, orchestrators, and plugins. Best for pattern-spotting: browse it to see how good setups are actually built.

Context & utility tools

yamadashy/repomix (~26k★, TypeScript) — packs an entire (or filtered) codebase into a single, token-optimized file for Claude Code to read. Remote-repo support, ignore patterns, GitHub Actions. Essential when your project is too big to fit in context naturally.

Vertical / niche

mukul975/Anthropic-Cybersecurity-Skills (~18k★, Python) — structured security skills mapped to common frameworks. A good example of going deep on one domain rather than broad — worth cloning if security is your surface.

Must-clone vs nice-to-have (honest tier list)

• Clone first (structure & reliability): superpowers or gstack (pick one as your spine), plus mattpocock/skills to adopt incrementally.
• Clone for breadth: awesome-claude-skills and awesome-claude-code as your skill/pattern sources.
• Clone when you hit the wall: repomix once your codebase outgrows the context window.
• Read, don't fork: anthropics/claude-code for understanding.
• Domain-only: the security skills if that's your world.

Don't clone all of them at once. One framework + one skill source + repomix is a complete, non-bloated setup.

Safety: read before you run

These repos ship hooks, commands, and skills that can execute shell commands automatically. Treat them like any third-party code:

• Read the hooks and commands before enabling them.
• Try them in a throwaway project or a branch first, not your live repo on day one.
• Never paste secrets into a session; keep keys in .env.
• Adopt incrementally — one skill, confirm it behaves, then the next.

New to installing skills and plugins? The skills & plugins guide covers the exact /plugin marketplace add and /plugin install commands, the official vs community marketplaces, and how to build your own.

Put it to use

Clone one framework, wire it into a real project, and ship:

• Structure it properly with the Claude Code projects hub.
• Pick something to build from the 15 project ideas with prompts.
• New to the tool? The beginner tutorial.
• Shipped it? List it free on SaaSCity and get your first builders looking.

FAQ

Best repos to clone in 2026? Start with superpowers or gstack for structure, mattpocock/skills for engineering discipline, the two awesome lists for breadth, and repomix for context. Read anthropics/claude-code to understand the foundation.

How do I use GitHub skills safely? Read the skills/hooks/commands first (hooks auto-run shell commands), test in a throwaway branch, never paste secrets, adopt one at a time.

Indie hacker vs team — where to start? Solo: gstack or mattpocock/skills. Team: superpowers layered onto your existing process.

Still worth it with official plugins? Yes — official gives you the engine, the community repos give you battle-tested workflows and big skill libraries. Most setups combine both.