Everything Claude Code is an open source project that has crossed 236,000 stars on GitHub, making it the most starred configuration repository for AI coding assistants. Created by developer Affaan Mustafa and launched publicly in January 2026, the toolkit turns Claude Code, OpenAI Codex, Cursor and other tools into smarter, more disciplined code agents. Instead of a single chatbot, developers get a full virtual team with specialized roles, rulebooks and safety checks.
How Everything Claude Code Works
It is not a standalone app or library. It is a plugin and configuration system that layers hooks, reusable skills, language-specific coding rules and predefined agent personas on top of existing AI assistants. Think of it as giving a team of software engineers a laptop and then adding a coding standard handbook, a security checklist and dedicated architect, reviewer and tester roles. That is what it does for Claude Code and others.
The project ships as a Claude Code plugin installed with two slash commands. Once loaded it provides a suite of what the maintainer calls an agent harness performance optimization system. The Medium article notes three standout design decisions. Hook runtime controls let developers switch between minimal, standard and strict profiles with an environment variable. Cross platform parity means the same repository provides configs for Claude Code, Cursor, OpenCode and Codex simultaneously. And NanoClaw v2, the built-in agent orchestration layer, handles model routing, skill loading and session management so the agent behaves more like a coordinated system than a lone responder.
Under the hood, the toolkit bundles hundreds of files. The GitHub repository shows folders for agents, skills, rules and hooks. Agents folder contains 15 role definitions such as code reviewer, security auditor, architect and test engineer. Each is a markdown file with a specific prompt that tells the AI how to behave. The skills folder teaches the AI reusable workflows like self evaluation or test-driven development. The rules folder holds language-specific conventions for TypeScript, Python, Go, Rust and more. Hooks trigger automatic actions before or after operations such as running linters or blocking unsafe commands.
The Hackathon Win Behind Everything Claude Code
Affaan Mustafa and a teammate won the Anthropic x Forum Ventures hackathon in NYC by building zenith.chat entirely with Claude Code in eight hours. The prize was $15,000 in API credits. The configuration setup they used during that sprint became the foundation of the project. Soon after, Mustafa published “The Shorthand Guide to Everything Claude Code” on X. The thread received 900,000 views and over 10,000 bookmarks within days.
Mustafa open-sourced the entire configuration system after that viral moment. By March 2026 the project had hit version 1.8.0 and its description shifted from a personal config pack to an agent harness performance optimization system. The repository now runs 997 internal tests across agents, skills, hooks and rules. The early momentum carried it from a hackathon artifact to a GitHub project with over 35,900 forks according to the GitHub repository.
The community that formed around the project has not always agreed. A Medium investigation notes that the Reddit developer community, especially r/ClaudeCode with its 4,200 weekly contributors, splits sharply in both directions. Some call it an indispensable layer that makes agents far more reliable. Others argue the configuration complexity adds overhead that undermines the simplicity of working with an AI assistant. The debate about whether the toolkit is essential or over-engineered continues to fuel its visibility.
Cross Platform Support and NanoClaw v2
One of the most valued design goals is working across multiple coding environments instead of locking into a single assistant. ECC provides the same commands, hooks and rules whether a developer uses Claude Code, Codex, Cursor or OpenCode. The Medium article reports that formal four-platform support arrived in version 1.6.0. Version 1.8.0 then tightened behavioral consistency across all four tools. A Cursor user gets a .cursor directory, an OpenCode user gets .opencode and a Codex user finds .codex plus an AGENTS.md file. This avoids the fragmentation that comes from maintaining separate configs for each assistant.
NanoClaw v2 is the component that pushes ECC from a collection of config files into something closer to an operating system for agents. It routes tasks to the right model automatically, hot-loads skills at runtime and manages sessions with branching, searching, exporting and compacting. The agent keeps a persistent memory so it remembers project context across conversations. An experimental plugin marketplace for Codex is also in place though this remains experimental. Our earlier coverage of Buzz, an open source workspace built around agents as teammates, explores the same idea of teams of AI agents from a different angle.
The repository continues to evolve quickly. The most recent commits show work on a hosted security dashboard, a proximity visualization for agent airspace and monetization roadmaps. All of it remains open source with a public testing harness. The maintainers encourage reproducible benchmarks and include the testing tools inside the repo so anyone can verify claims.
Installation Hurdles and Community Response
Getting Everything Claude Code running is generally quick with two slash commands for Claude Code users. But a known gotcha trips up new adopters. Claude Code version 2.1 and later automatically loads hooks.json from installed plugins. If a user also declares a hooks field in the .claude-plugin/plugin.json file, the system throws duplicate detection errors. The fix is straightforward: do not manually declare hooks. The plugin system handles it. The same article notes that this issue appears repeatedly across GitHub Issues #29, #52 and #103.
Another limitation frustrates users who expect an all-in-one install. Claude Code’s plugin system cannot distribute rules automatically. When it is installed as a plugin, agents, commands, skills and hooks all load automatically. Rules do not. Developers must copy them manually into the project’s .claude/rules/ directory. This breaks the “install once get everything” promise and creates friction for newcomers.
The 236,000 stars on the GitHub repository nonetheless signal massive adoption. Many contributors have filed pull requests and opened issues that shaped the hook profile system and the cross-platform configs. Community energy drives rapid iteration but also fuels the split opinion. Some see a dense toolkit that finally gives AI agents the structure they need. Others see a project that has outgrown its hackathon roots and now demands too much from a developer who just wants a helpful code companion.
The Growing Everything Claude Code Ecosystem
The project now extends far beyond a single plugin. The repository links to ecc.tools, a dedicated domain, and includes a roadmap for a hosted Pro version with multi-repo agent security dashboards. The open source core remains free and the testing harness lets anyone independently verify performance claims. Affaan Mustafa continues as lead maintainer with dozens of contributors submitting patches and feature proposals.
The project’s trajectory shows how a hackathon victory can turn into a developer platform. It also highlights the tension between increasing agent capability and the simplicity users want. For teams that run Claude Code, Codex or Cursor daily, Everything Claude Code offers a structured way to enforce quality and security. Whether that structure is worth the setup cost remains a live debate in the community.
Everything Claude Code FAQ
What is Everything Claude Code exactly?
It is an open source plugin and configuration system for AI coding assistants. It adds hooks, skills, language rules and role-based agents on top of tools like Claude Code, Codex, Cursor and OpenCode. The project hit 236k GitHub stars and provides a way to make AI agents follow team-like workflows instead of reacting to single prompts.
Does ECC work with Cursor and Codex?
Yes. The repository includes dedicated config directories for Cursor, Codex and OpenCode alongside Claude Code. Cross-platform parity was a design goal from version 1.6.0 onward. A community report confirms the same commands and hooks are available across all supported editors.
How do I install Everything Claude Code?
Claude Code users can add the plugin via /plugin marketplace add affaan-m/everything-claude-code and then /plugin install everything-claude-code@everything-claude-code. For other editors the repo provides manual config copy instructions. A common installation pitfall involves duplicate hook detection so users should avoid declaring hooks in plugin.json.
