Everything Claude Code: What ECC Is and How to Install It

Everything Claude Code is a large open-source configuration pack for Claude Code: subagents, skills, slash commands, hooks, rules and a security scanner, all maintained in one GitHub repo. If you search for everything-claude-code on GitHub today, you land somewhere slightly different. The repo has been renamed to ECC, and the old URL redirects to github.com/affaan-m/ECC.

Here's the short version:

• What it is: an "agent harness" kit that gives Claude Code a plan, test, review and verify workflow instead of starting every session from scratch
• Who maintains it: Affaan Mustafa, under the MIT licence
• How to install it: as a Claude Code plugin (ecc@ecc), through a guided npx setup, or by copying only the pieces you want
• What to watch: it installs hooks that run shell commands as you, so read them before you turn them on

This guide covers what's actually in the repo, the install paths the README recommends, and how to keep a setup this big from flooding your context window.

What Everything Claude Code is

The repo's own description calls it "the agent harness performance optimization system." In practice it's a curated set of the files Claude Code already knows how to load: subagent definitions, skills, slash commands, hooks and rule files. ECC packages them so you can install one opinionated setup instead of writing each file yourself.

The workflow it pushes is spelled out at the top of the README:

plan -> test -> implement -> review -> verify -> remember -> improve

So instead of asking Claude to "please use TDD" and hoping it remembers, ECC wires that into a skill with a planner agent, a test-first guide and a fresh-context code reviewer.

The rename: everything-claude-code is now ECC

The GitHub API now returns affaan-m/ECC for the old affaan-m/everything-claude-code path, and the README explains that the project has three identifiers that aren't interchangeable:

Older blog posts and threads still show the long name and an older marketplace ID. The README treats those as legacy aliases. If a tutorial tells you to install something called everything-claude-code from a source that isn't the repo above, stop and check.

Licence and maintainer

The LICENSE file is MIT, copyright Affaan Mustafa. The README describes it as a single-maintainer project funded by sponsors and by a separate hosted GitHub App for private repos. The open-source repo itself stays MIT.

The current release at the time of writing is 2.2.3, published October 1, 2026, per the repo's releases page.

What's inside the repo

The README's own count, as of October 2026, is 71 agents, 311 skills and 97 legacy command shims, plus hooks, rules, memory tooling and a scanner called AgentShield. Those numbers move with almost every release, so treat them as "a lot" rather than a spec.

If those building blocks are new to you, they map one-to-one onto Claude Code's own features. Skills work the way they do in any Claude skills setup, and the agents are standard subagent files with frontmatter.

It isn't only for Claude Code

ECC's README says it "works best with Claude Code today" and ships native Codex and Qoder plugin paths, plus thinner adapters for Cursor, OpenCode, Gemini, Zed, GitHub Copilot and others. Its own support matrix marks Claude Code as "Stable primary" and most other harnesses as beta or experimental, without full feature parity. If you mostly use Cursor, expect a subset.

How to install Everything Claude Code

The README is firm on one point: pick one install method per tool and don't stack them. Installing ECC twice into Claude Code duplicates skills, commands and hooks.

Option 1: the guided setup

The recommended path needs Node.js 18 or newer, Git, and Claude Code 2.1 or newer on your PATH:

npx ecc-universal@2.2.3 setup

The wizard asks for a scope (global user, project or local) and a hook profile, then installs the ecc@ecc plugin. Run the same command later to update, change scope or change the hook profile. Swap the version number for whatever the README lists when you install.

Option 2: native plugin commands

If you'd rather use Claude Code's own plugin system, run these inside a session:

/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc@ecc

That installs the skills, agents, commands and plugin-managed hooks. Afterwards, commands are namespaced, so the planner runs as /ecc:plan "describe the feature". Our Claude Code plugins guide covers how marketplaces and scopes work if this is your first plugin.

Adding rules by hand

Claude Code plugins can't distribute rule files, so ECC asks you to copy them yourself:

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/

Start with common plus one pack for the language you actually write. Rules load into every session, so each extra pack costs context.

Option 3: a low-context install with no hooks

If you want ECC's agents, skills and rules but not its runtime hooks, the README offers a minimal profile:

npx ecc-universal@2.2.3 install --profile minimal --target claude

This is the path to pick if you want to try ECC without anything running automatically. You can add the hook runtime later with an explicit --enable-hooks flag. You can also install single skills, for example --skills tdd-workflow,security-review from a checkout.

Uninstalling

The npm package includes list-installed, doctor, repair and uninstall commands, and uninstall --dry-run shows what it would remove first. Plugin users remove the plugin in Claude Code, then delete any rule folders they copied by hand.

Read this before you install third-party hooks

ECC is popular (the repo has hundreds of thousands of GitHub stars) and actively maintained, and its README is unusually candid about risk. That's still not a reason to skip a review, because of what plugins and hooks can do.

Anthropic's plugin security page puts it plainly: a plugin you install "can execute arbitrary code on your machine with your user privileges." The hooks reference adds that command hooks can modify, delete or access any file your account can reach. Permission rules and the sandbox cover Claude's tool calls, not the hook scripts a plugin runs on its own.

A practical checklist:

1. Install only from the official source. ECC's README warns that third-party re-uploads and mirrors "may contain malware." Its verified channels are the GitHub repo, the ecc-universal and ecc-agentshield npm packages, the ECC Tools GitHub App, the ecc@ecc plugin slug and the ecc.tools website.
2. Read hooks/hooks.json and the scripts it calls. Know what runs on session start, before tool calls and at session end.
3. Start without hooks, or with the default profile. The ECC_HOOK_PROFILE and ECC_DISABLED_HOOKS environment variables let you dial strictness down or switch off individual hooks.
4. Pin a version and re-review on update. If marketplace auto-update is on, the files you reviewed can change on disk.
5. Notice anything that sends code elsewhere. The optional /astra-review command, for example, sends your diff to OpenAI through the Codex CLI. The README says so, but it's easy to miss.

Our Claude Code hooks guide explains the events and matchers if you want to understand what each ECC hook is actually doing.

How to use ECC without drowning in it

The biggest practical complaint about mega-configs is context bloat. ECC's own platform notes say the plugin "advertises the installed catalog to the model" and point to a selective install when context footprint matters.

A sensible way in:

Use it for a week with one or two workflows. Then delete what you never touched.

FAQ

What is Everything Claude Code?

It's an open-source collection of Claude Code agents, skills, commands, hooks and rules maintained by Affaan Mustafa. The project now goes by ECC, and the old everything-claude-code GitHub URL redirects to affaan-m/ECC.

Is everything-claude-code on GitHub official Anthropic software?

No. It's a third-party community project. Anthropic's own marketplaces use reserved names, and ecc@ecc isn't one of them.

Is Everything Claude Code free?

The repo is MIT-licensed. The maintainer also sells a separate hosted GitHub App for private repos, which you don't need to use the open-source configs.

How do I install everything-claude-code?

Run the guided npx ecc-universal setup command, or add the marketplace with /plugin marketplace add https://github.com/affaan-m/ECC and install ecc@ecc. Choose one method, not both.

Does ECC work with Cursor or Codex?

Codex and Qoder have native plugin paths. Cursor, OpenCode, Gemini and several others get project-level adapters that the README labels beta or experimental, without full Claude Code parity.

Can I install only part of ECC?

Yes. Use the minimal profile, install named skills with --skills, or copy individual agent and skill folders into ~/.claude/. That's often the better choice than the full catalog.

The short version

Everything Claude Code, now ECC, is one maintainer's very large, MIT-licensed take on how Claude Code should work: plan first, test first, review with fresh context. Install it once through the plugin or the guided setup, add one rule pack, and read the hooks before they run.

If you like the idea of borrowing a proven setup but don't want to manage plugins, rule folders and hook profiles yourself, that's the gap Taku is built for. It's an AI-native desktop workspace where you mirror an AI app, skill or workflow someone else already got working, run it, and remix it into your own. Taku is in Beta, and the Mac app is available now.