Everything Claude Code (ECC): install it, and what to check first
The GitHub project once called everything-claude-code is now ECC. How its README installs it, what it adds to Claude Code, how to verify and undo it.
- For
- Claude Code users who found the everything-claude-code repository
- Written for
- Claude Code, Codex
- Time
- 9 min read · updated Nov 21, 2026
The short answer
The repository called everything-claude-code is now affaan-m/ECC, an MIT-licensed bundle for coding agents: 328 skill folders, 72 agents, 99 command shims, and hooks. Its README’s recommended install for Claude Code is npx ecc-universal@2.2.3 setup, which installs a plugin named ecc@ecc; the plugin commands /plugin marketplace add https://github.com/affaan-m/ECC and /plugin install ecc@ecc give the same plugin. Pick one route, because the README warns against stacking a manual install on top. Before you run either, read hooks/hooks.json: the plugin registers 28 hook entries that run node commands on your machine.
Searching for “everything claude code” usually ends at one GitHub repository that has changed its name. It was called everything-claude-code; GitHub’s API still answers at that name and returns affaan-m/ECC, which is the name in the README and the one you will see in install commands. This page reads that repository’s README, manifests and hook file, the npm package it installs from, and Claude Code’s plugin documentation, all on 21 November 2026. We did not install ECC for this page, so it tells you what the files say and what to check, not whether it will make your agent better.
What it is
The README describes ECC as an engineering system and toolbox for coding agents: plan, test, implement, review, verify, remember. In the repository that is a lot of files. On the day we looked, the skills/ folder held 328 folders, agents/ held 72 and commands/ held 99, which matches the counts in the plugin’s own manifest. It also ships hooks, rules, a memory system and a security scanner it calls AgentShield. The repository is MIT licensed, the latest release is v2.2.3 from 1 October 2026, and the last push in our check was on 20 November 2026.
It is built for Claude Code first. The README says it has native paths for Codex and Qoder, and lighter adapters for Cursor, OpenCode, Gemini, Copilot and others, and it points to a support matrix before you assume every feature carries over. The README also describes a separate hosted product, ECC Pro, as a GitHub App for private repositories; the repository itself stays MIT.
Two ways to install it in Claude Code
The README gives two routes for Claude Code and says both install the same plugin, ecc@ecc. Choose one.
In a session, /plugin install does not install straight away. Claude Code’s documentation says it opens the /plugin panel on the plugin’s details so you can review it and choose a scope first, and it adds that a plugin can run hooks and MCP servers, so you should read the pane. Best Claude Code plugins explains the panel and the three scopes.
The README’s own check is to start a new session and run /plugin list to confirm that ecc@ecc is enabled. Claude Code’s docs describe two checks you can rely on: the Installed tab in /plugin, and claude plugin list in a shell, which prints a Version, Scope and Status line for each plugin.
What it adds to your sessions
Skills and agents are files Claude Code lists and loads when relevant. The part that changes how a session behaves is the hook file. hooks/hooks.json in the repository registers 28 entries across eight events: ten on PreToolUse, eight on Stop, two each on SessionStart, UserPromptSubmit, PostToolUse and PostToolUseFailure, and one each on PreCompact and SessionEnd. All 28 run a node -e command. That is a lot of code firing around your tool calls, which is why the README’s own Security section says hooks can run shell commands and should be treated as executable configuration.
Context is the other cost. The README says to start with the workflow you need rather than the full catalog, and it points to a /context-budget command and to removing rules you do not need. Claude Code can measure part of this for you: in your shell, claude plugin details <name> prints an Always-on line, which its docs define as the tokens the plugin adds to every session where it is enabled, with the biggest contributors listed per component. Run it on ecc after you install, and decide from the number.
What the install runs
The guided setup is a package you run with npx. We looked at the registry entry for ecc-universal 2.2.3: it is MIT licensed, needs Node.js 18 or newer, holds 2,805 files, and its package.json lists no preinstall, install or postinstall script. That tells you nothing happens just from downloading it, and nothing about what the setup command does once it runs, which is the part to read. The README adds its own caution: a pinned version is not a security audit or an integrity check, so review the release source before running package code. It also says to install ECC only from its official channels: the GitHub repository, the two npm packages ecc-universal and ecc-agentshield, the GitHub App, and the plugin name ecc@ecc.
Turning it off or removing it
- Turn it off.
claude plugin disable ecc@eccin a shell, or the Installed tab in/plugin. Disabling keeps the files and stops the plugin from loading. - Remove the plugin.
claude plugin uninstall ecc@ecc. If you installed through the guided setup and used a project folder, also run the ECC uninstall from that same folder. - Check what ECC thinks it installed. The README’s reset section lists
list-installed,doctor,repair,uninstall --dry-runanduninstall, all run asnpx ecc-universal@2.2.3 <command>. It says ECC only removes files it recorded in its install-state, and leaves unrelated files in your agent folders alone.
A bundle, or one skill
ECC is a harness-sized bundle: it changes how the agent plans, tests, reviews and remembers, across hundreds of skills. That is a different thing from a single skill folder you copy into ~/.claude/skills/, and the safety check is different too: with one skill you read one SKILL.md and its scripts, with ECC you are also reading a hook file and a setup program. Safety checks before running a skill lists what to look for in either, and Superpowers for Claude Code is a smaller plugin of the same kind if you want to compare. Neither bundle produces a deliverable you open afterwards.
Skills that make a finished file
Lookbk’s skills do the other job: each one renders a file, such as a landing page, a slide deck, a link-preview image or a title video, and its page shows what it made. They are plain skill folders, so they sit alongside any plugin. These four are free.
Run the installer from inside Claude Code with the last part of a skill page’s address; it writes to ~/.claude/skills, the folder Claude Code reads.
Common questions
- Is everything-claude-code the same as ECC?
- Yes. The repository was named everything-claude-code and is now affaan-m/ECC; GitHub’s API still answers at the old name and returns the new one. Inside Claude Code the plugin is called
ecc@ecc, and the npm package isecc-universal. - How do I install Everything Claude Code in Claude Code?
- The README’s recommended route is
npx ecc-universal@2.2.3 setup. Or, inside Claude Code,/plugin marketplace add https://github.com/affaan-m/ECCand then/plugin install ecc@ecc. Both install the same plugin; choose one. - Is ECC free?
- The repository is MIT licensed. The README also describes ECC Pro, a separate hosted GitHub App for private repositories, which the plugin install does not require.
- Does ECC run code on my machine?
- Its hook file registers 28 entries across eight events, and each one runs a
node -ecommand. The README’s Security section says to treat hooks as executable configuration. Readhooks/hooks.jsonand use the hook profile settings before you enable it. - How do I check that ECC installed?
- The README says to start a new session and run
/plugin list, looking forecc@ecc. Claude Code’s docs also describe the Installed tab in/pluginandclaude plugin listin a shell. - Can I install ECC in Codex too?
- The README says yes: its multi-agent guided install covers Claude Code, Codex and Kimi Code, and Codex has its own plugin commands. It says to choose one install method for each agent, and that installing once into several agents does not duplicate anything.
- How do I remove ECC?
claude plugin uninstall ecc@eccremoves the plugin. If you also used the guided setup in a project folder, the README’s reset section listsnpx ecc-universal@2.2.3 uninstall --dry-runanduninstall, which only remove files ECC recorded.
Sources
What this guide says about other companies’ tools comes from their own documentation, checked on Nov 21, 2026.
Did this guide help?
Read next
All guidesSafety checks before running a skill
A skill is instructions and code your agent may run. Six checks to make first: its source, its commands, its network use and what it may do without asking.
Claude Code plugins: install them, and the best ones
Claude Code plugins explained: browse the marketplace, install one with /plugin, pick a scope, then the best plugins by job, each checked at its source.
Superpowers for Claude Code: how to install it and what it adds
How to install the Superpowers plugin in Claude Code, the two routes and how they differ, the 15 skills and the session hook it adds, and how to turn it off.
Claude Code plugin marketplace: build and host your own
How to build a Claude Code plugin marketplace: the marketplace.json fields, plugin sources, claude plugin validate, reserved names, and where to host it.
Update, roll back and remove skills
Update an installed skill, go back to the version you had, and remove or switch off a skill in Claude Code, Codex, Cursor, Copilot, Gemini CLI or OpenCode.
See a skill’s result before you install it.
Every skill page shows what it makes, what it needs and which agents can run it.



