Everything Claude Code: What's in It and How to Install
Everything Claude Code (now ECC) reviewed: what the GitHub repo ships, its MIT licence, the install commands, and what to check before running its hooks.
Josh Pocock7 min read
AI Coding
Everything Claude Code
Stride AI Academy
Everything Claude Code is an open-source, MIT-licensed collection of agents, skills, commands, hooks and rules for Claude Code. The project now goes by ECC, and the old everything-claude-code GitHub URL redirects to github.com/affaan-m/ECC. You install it as a Claude Code plugin, either with its guided npx setup or with two /plugin commands, and you can skip the hooks if you only want the agents and skills.
This guide covers what the repo contains, the install paths its README documents, how to install only part of it, and what to read before you let third-party hooks run on your machine. Everything here was checked against the ECC repository and README and Claude Code's docs on installing plugins, plugin security and hooks on November 22, 2026. The repo ships weekly, so check the README for the current version before you copy a command.
What is Everything Claude Code?
The README describes ECC as a system that makes your agent plan before it builds, verify changes with tests, review its own work from a fresh context and remember what matters. It works best with Claude Code, has native plugin paths for Codex and Qoder, and has lighter adapters for Cursor, OpenCode, Gemini, Zed, GitHub Copilot and other tools.
On November 22, 2026, the GitHub API showed the repo with 308,507 stars and 45,392 forks, an MIT licence and a last push on November 20, 2026. The README says the open-source repo stays free and separately sells a hosted GitHub App for private repos, which its pricing page lists at $19 per seat per month for the Pro plan.
What's in the everything claude code GitHub repo
The README lists these parts on November 22, 2026:
| Part | README count | What it does |
|---|---|---|
| Agents | 72 | Subagents for planning, review, build repair, security and architecture |
| Skills | 328 | Workflows such as TDD, research, security, docs and frontend |
| Commands | 99 legacy shims | Older slash commands, kept while the project moves to skills |
| Hooks and memory | Runtime | Session summaries, learned "instincts" and context controls |
| Rules | Pick per language | Always-loaded standards in rules/common/ plus language folders |
| AgentShield | Included | Scans prompts, hooks, MCP config, permissions and secrets |
If those terms are new, they map onto standard Claude Code features. Agents are subagents, skills are Claude Code skills, and hooks are shell commands that fire on tool events, covered in our Claude Code hooks tutorial. ECC packages all of them as a single plugin, so our Claude Code plugins guide explains how it loads.
Before you install
The README lists three requirements for the guided setup:
- Node.js 18 or newer
- Git
- Claude Code 2.1 or newer on your PATH
It also warns you to install only from its official sources: the GitHub repo, the npm packages ecc-universal and ecc-agentshield, its GitHub App, the plugin name ecc@ecc and its website. It says third-party re-uploads and mirrors aren't reviewed by the project and may contain malware. Many forks and copies of the repo exist on GitHub, so check the owner in the URL before you run anything.
How to install Everything Claude Code
The README gives two ways to install the same ecc@ecc plugin. Pick one. It says stacking install methods duplicates skills, commands and hooks.
Option 1: guided setup
npx ecc-universal@2.2.3 setupThe wizard checks your existing Claude Code install scopes, then installs or updates the plugin at the scope you pick. For a personal setup, the README suggests choosing Global user and the Standard hook profile. Afterwards, start a new Claude Code session and confirm it loaded:
/plugin listOn Windows, the README's walkthrough runs the same command from PowerShell after checking node --version, git --version and claude --version. If you haven't set up Claude Code there yet, start with our Claude Code on Windows guide.
Option 2: Claude Code's plugin commands
Inside a Claude Code session:
/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc@eccClaude Code's own install flow opens the plugin's details pane before it installs, so you can read the Will install list and choose user, project or local scope. That pane is the moment to check what hooks and MCP servers you're about to turn on.
Add rules by hand
Claude Code plugins can't distribute rules, so the README has you copy the ones you want:
git clone https://github.com/affaan-m/ECC.git
cd ECC
mkdir -p ~/.claude/rules/ecc
cp -R rules/common ~/.claude/rules/ecc/
cp -R rules/typescript ~/.claude/rules/ecc/Swap typescript for your own stack. Rules load into every session, so the README advises starting with common and one language pack only.
How to install only the parts you need
You don't have to take the whole catalog. The README documents three narrower paths.
No hooks at all. The minimal profile installs rules, agents, commands and core workflows without the hook runtime:
npx ecc-universal@2.2.3 install --profile minimal --target claudeAsk which parts fit your work. The packaged advisor returns matching components and the command to preview them:
npx ecc-universal@2.2.3 consult "security reviews" --target claudeCopy files by hand. From a clone, each part is independent, so you can copy only the agents:
mkdir -p ~/.claude/agents
cp agents/*.md ~/.claude/agents/The README notes that Claude Code finds skills only as direct children of ~/.claude/skills/, so don't nest copied skills inside an ecc folder.
What to check before you run third-party hooks
This is the part to slow down on. Claude Code's plugin security page says a plugin you install "can execute arbitrary code on your machine with your user privileges." Its hooks run as shell commands with your full user permissions, outside the sandbox, and your permission rules don't cover them.
Before you install, the docs suggest you:
- Run
claude plugin marketplace listto confirm where the marketplace came from. - Read the Will install section in the
/plugindetails pane. - Read the plugin's source:
hooks/hooks.jsonfor each hook's command,.mcp.jsonfor each server, and every file inbin/. - List what Claude Code finds in a clone without starting a session:
claude --plugin-dir <plugin directory> plugin details <plugin name>ECC's own installer helps here. For a manual install, it stops before writing any hook unless you pass --enable-hooks or --no-hooks, and prints what the hooks can do. It also tells you not to copy the repo's hooks/hooks.json into your settings.json, because Claude Code already loads a plugin's hooks and a copy runs them twice.
After install, run /hooks in a session. The docs describe it as a read-only browser that labels each hook with its source, including which plugin added it. To switch every hook off without removing it, set this in your settings file:
{
"disableAllHooks": true
}One more thing to know: the docs say auto-update is off by default for third-party marketplaces. If you turn it on, the files you reviewed can change on disk later.
How to uninstall ECC
For the guided install, the README lists these commands, run from the same project directory:
npx ecc-universal@2.2.3 uninstall --dry-run
npx ecc-universal@2.2.3 uninstallFor the plugin path, remove it with Claude Code:
claude plugin uninstall ecc@eccThen delete any rule folders you copied by hand. If you stacked install methods, the README says to remove the plugin first, run ECC's uninstall, delete extra rule folders, then reinstall once using a single path.
Should you install it?
ECC is a large, opinionated setup. It suits you if you want a ready-made planning, testing and review routine and are happy to read through what it adds. If you prefer a small setup you understand line by line, take one or two pieces, such as a reviewer agent or a rule pack, and build the rest yourself. Either way, Claude Code works without it, and our Claude Code guide covers the built-in features first.
Learn to build with Claude Code
The Stride AI Coding course teaches Claude Code and Codex for building client tools, written for non-programmers, with weekly live calls to review your builds. Many of the free guides cover Claude Code setups, and the Claude Code community is where members compare theirs.
FAQ
What is Everything Claude Code?
It's an open-source, MIT-licensed collection of agents, skills, commands, hooks and rules for Claude Code, also usable with Codex and other tools. The project is now called ECC, and the old repo URL redirects to github.com/affaan-m/ECC.
Where is the everything claude code GitHub repo?
It's at github.com/affaan-m/ECC. The README warns that re-uploads and mirrors aren't maintained by the project, so check the owner in the URL before installing.
How do I install Everything Claude Code?
Run npx ecc-universal@2.2.3 setup, or inside Claude Code run /plugin marketplace add https://github.com/affaan-m/ECC and then /plugin install ecc@ecc. Use one method only, then run /plugin list in a new session to confirm it loaded.
Can I install ECC without hooks?
Yes. The README's minimal profile, npx ecc-universal@2.2.3 install --profile minimal --target claude, installs the rules, agents, commands and core workflows without the hook runtime.
Is it safe to install a third-party Claude Code plugin?
Claude Code's docs say a plugin can run code with your user privileges, and its hooks run outside the sandbox. Read its hooks/hooks.json, .mcp.json and bin/ folder before installing, and check the details pane in /plugin.
Is Everything Claude Code free?
The repo is MIT-licensed and free to use. The README separately sells a hosted GitHub App for private repos, priced from $19 per seat per month on November 22, 2026.