← mods directory○ community

Mod · hesreallyhim

awesome-claude-code.

Every healthy ecosystem grows an awesome-list. This one is the single pane of glass over the community's best Claude Code work, and where most of the rest of this directory came from.

If you only follow one Claude Code resource, follow this one. awesome-claude-code is a curated index of skills, hooks, slash commands, agent orchestrators, applications, plugins, and statuslines, sorted by extension type, lightly opinionated about quality, and updated more often than most official docs.

It is curation, not content. Almost nothing original lives in the repo itself; it is a map. But the map is good, the categories make sense, and the PR-review bar is high enough that the bad stuff gets filtered before it lands. Treat it as your weekly browse.

§01What's in there

The list is broken into the categories that actually exist in the Claude Code extension model:

  • Skills, which is the bulk of the list, ranging from creative (algorithmic-art, theme-factory) to productive (skill-creator, brand-guidelines) to domain-specific (Corey Haines's marketing stack).
  • Hooks, the lifecycle scripts that run on tool use, session start and end, errors, and so on.
  • Slash commands, bundled command packs that add prompts and shortcuts.
  • Agent orchestrators, multi-agent setups that coordinate subagents.
  • Applications, full apps built with or around Claude Code.
  • Plugins and statuslines, the UI and UX mods. Claude HUD lives here.

§02How to actually use it

The temptation is to skim awesome-lists like a buffet. The mistake is doing exactly that. A more productive approach is to treat the list as a research roadmap. Pick one category at a time, say only hooks for the week. Open the top three by stars and read their READMEs end to end. Install one and use it for a week, then decide if it stays. Repeat with the next category the following week.

Three months in, the result is an opinion on which extension types actually move the needle for your workflow and which are noise. That opinion is more valuable than any single mod on the list.

§03Caveats

  • Lists go stale. Always check last-commit dates on the linked repos before installing. Anything dormant for more than six months is suspect.
  • Stars are not the same as quality. The PR-review filter is good but not perfect. Read the code on anything you are going to give filesystem or shell access to.
  • It is not exhaustive. A missing entry does not mean a missing tool; some great mods just have not been submitted. The list is a useful map, not the territory.