What is Everything Claude Code (ECC)? What's inside, installation, hooks and pricing
Instead of steering Claude Code from scratch in every project, you install the Everything Claude Code (ECC) kit: it brings ready-made agents that plan, write tests and review code, along with skills, commands, hooks and rules. According to the current README, it has 71 agents, 311 skills and 97 command files (version 2.2.3). The recommended installation is `npx ecc-universal@2.2.3 setup`; the official package name is ecc-universal, and packages named "everything-claude-code" are not official. Because hooks run commands on every tool call, it is wiser to start with the lightweight profile than to install everything blindly. MIT-licensed; the software is free.
- What it does
- Adds ready-made agents, skills and commands to Claude Code
- Type
- Kit: a pack of agents, skills, commands, hooks and rules
- Where
- Claude Code (primary), Codex, Qoder; Cursor and OpenCode in beta
- Contents
- 71 agents, 311 skills, 97 commands, 27 hook entries
- Hooks
- Run commands on every tool call
- Turkish
- Not stated in official sources
- Cost
- Software is free (MIT); the GitHub App is separate and paid
What does ECC do? What's inside?
A pack written to set up a ready-made team instead of steering Claude Code from scratch in every project: agents that plan, write tests first, review code and fix build errors; skills and commands that call them; hooks attached to tool calls; and language-specific rules. The counts in the official directory, which the README also states:
| Part | Count | What |
|---|---|---|
| Agents (agents/) | 71 | planner, architect, code-reviewer, security-reviewer, tdd-guide, build-error-resolver and language-specific reviewers (TypeScript, Python, Go, Java, Rust and others). |
| Skills (skills/) | 311 | TDD, security, research-first, API design, database migrations, framework patterns, content writing and more. |
| Commands (commands/) | 97 | Slash entries such as /plan, /code-review, /build-fix, /learn and /checkpoint. README: skills are the main surface, commands are transitional shortcuts. |
| Hooks (hooks.json) | 27 entries | Command checks, config file protection, formatting and type checking, session summary, cost tracker. |
| Rules (rules/) | 122 files | Common rules and 22 language/framework folders. Not included with the plugin, copied by hand; this is context loaded in every session. |
Who it helps: people who write code regularly with Claude Code and want a ready-made workflow. For a small task, most of it is unnecessary; the README itself recommends using the parts you need rather than the whole catalog.
How do you install ECC?
!The official package name is ecc-universal. ECC's SECURITY.md file tells you not to install packages under "everything-claude-code" or similar alias names unless they are officially documented.
Prerequisites (README): Node.js 18+, Git and Claude Code 2.1+. The commands are taken verbatim from the README.
› npx ecc-universal@2.2.3 setupThe wizard asks for the scope (user, project, local) and hook level (off, minimal, standard, strict). After installing, open a new Claude Code session and confirm with /plugin list that ecc@ecc is enabled.
› npx ecc-universal@2.2.3 install --profile minimal --target claudeThe README says this profile deliberately leaves out the hooks-runtime module. To add hooks later, use --modules hooks-runtime --enable-hooks.
In an installation that requires hooks, if you don't decide on --enable-hooks or --no-hooks, the installer stops without writing anything.
› /plugin marketplace add https://github.com/affaan-m/ECCThen /plugin install ecc@ecc. The plugin can't distribute rule files; you copy the rules by hand separately. The README says that if you chose this route, you shouldn't do a full manual install on top of it ("Do not stack install methods").
› ./install.sh --target claude --skills tdd-workflow,security-review› node scripts/ecc.js consult "security reviews" --target claude› codex plugin marketplace add affaan-m/ECCThen codex plugin add ecc@ecc. Codex hooks require an explicit trust decision and don't use Claude's hook profiles.
| Profile | What it's for |
|---|---|
| minimal | No hooks, lightweight; for getting started. |
| core, developer, security, research | Sets that expand by purpose. |
| opencode, full | For OpenCode, and all modules (33 modules). |
Start with --profile minimal or only the skills you need. npx ecc-universal@2.2.3 uninstall --dry-run shows in advance what will be removed.
How do you use ECC?
With the plugin, commands are namespaced (for example /ecc:plan). Skills kick in automatically when Claude finds them relevant to your request, or you call them by name.
› agentshield scan --path .Check installation health with npx ecc-universal@2.2.3 doctor and fix breakage with repair; list-installed lists what is installed.
Which programs does ECC work in?
| Claude CodeYes | README: stable primary target (Claude Code 2.1+). |
|---|---|
| Codex, QoderYes | Supported as a native plugin. |
| Cursor, OpenCode, GitHub Copilot CLIBeta | Beta adapter; full feature parity is not claimed. |
| Gemini CLI, Zed, Antigravity, Kimi Code and othersPartly | Experimental or minimal support; Copilot Chat is instructions only. |
| Native WindowsPartly | The README says "supported with limitations"; the WSL route is supported as core. |
The list is compiled from the platform table in the README.
What does ECC access, and what do the hooks run?
Hooks run commands on every tool call and at the end of every response (mostly Node scripts, some Bash or Python). Examples: command checks, formatting and type checking, pre-commit checks, session summary. ECC's own README tells you to treat hooks, MCP and project instructions as "executable configuration".
In a manual install, skill, agent, rule and command files under ~/.claude; hook entries in settings.json. Session summaries and metrics are kept under ~/.claude by default.
ECC doesn't delete files; uninstall only removes the files in its own installation record. The GateGuard hook gates destructive shell commands (such as rm) before they run; this is a block.
The scripts run locally. /astra-review sends your code diff to OpenAI (the README's own sentence). AgentShield's --opus analysis can also send data out. The GitHub App analyzes commit history and sample files in memory and says it doesn't store them persistently.
It also affects context: the plugin's installed catalog is reported to the model, and rules are context loaded in every session. The SessionStart hook adds up to 8,000 characters of context per session by default (turn it off with ECC_SESSION_START_CONTEXT=off).
| To scale back hooks | What it does |
|---|---|
ECC_HOOKS_ENABLED=false | Turns hooks off. |
ECC_HOOK_PROFILE=minimal | Lightens the hook profile. |
ECC_DISABLED_HOOKS="<ids>" | Turns off specific hooks. |
!There is a risk of thinking you turned hooks off while they stay on: an open report says the hooks_enabled=false value in the plugin settings isn't applied at runtime (issue #3279, version 2.2.2; the documentation doesn't say whether it was fixed in 2.2.3). The reliable route is the environment variable or the minimal profile without hooks. No published advisory appears in GitHub Security Advisories. That doesn't mean "safe"; review the repository or release source before installing (README: "pinning a version is not a security audit").
Is ECC free?
The software itself is free: the repository and npm package are MIT-licensed, and no payment is needed to use ECC on your own computer. What's paid is the separately hosted "ECC Pro" GitHub App, a service that analyzes your repositories. Prices are in US dollars. Claude Code's own subscription limits apply separately.
- Public repositories only
- 10 analyses per month
- Private repositories
- Private repository analysis
- 50 analyses per seat per month
- AgentShield-supported scanning
- SSO
- Unlimited analyses
- SSO-ready governance
- SLA
Source: ecc.tools pricing page and README. The paid service is subject to separate terms; read them before using it. The README carries sponsor logos and an affiliate link (aff=ecc). This is not legal advice.
Common problems and fixes
| What happens | What to do |
|---|---|
| A skill, command or hook runs twice | It was installed into the same agent by two methods. Remove the plugin, run uninstall, delete extra copied rule folders and reinstall with a single method. |
| Reported by users The wizard stops with a "Could not verify ecc@ecc…" error (macOS, 2.2.3) | Open issue #3492; no official fix is written. Resolve local plugin commands or the scope conflict and try again. |
| Reported by users On native Windows, hooks time out on every tool call | Open issue #3459: a lock gets stuck in Git Bash. Try the WSL route. |
| Reported by users An "unknown key in hooks.json" warning at startup | Reported on an older version (#3169); the README says the fields now live in a separate file. Whether it is resolved in 2.2.3 is unclear. |
| You're searching npm for a package named "Everything Claude Code" | The official package is ecc-universal; don't install alias packages. |
How do you uninstall ECC?
- If you installed with the plugin: Remove the
ecc@eccplugin from Claude Code. - If you installed with the wizard or by hand: Check what will be removed with
npx ecc-universal@2.2.3 uninstall --dry-run, then rununinstall. - Rules you copied by hand: Delete the
~/.claude/rules/eccfolder yourself; ECC doesn't count them as recorded. - Cancel the GitHub App: From the ecc.tools billing portal (documentation: cancel anytime).
Frequently asked questions
What is Everything Claude Code?
An MIT-licensed open-source kit that adds a ready-made pack of agents, skills, commands, hooks and rules to Claude Code. According to the current README, it contains 71 agents, 311 skills and 97 command files.
Is ECC paid?
The repository and npm package are MIT-licensed and free. What's paid is the separately hosted ECC Pro GitHub App: $19 per user per month for private repositories. No payment is needed to use it on your own computer.
Should I install everything, or pick individual parts?
Both are possible. The wizard installs a profile; for individual parts there is --skills a,b or copying by hand. The README recommends using the parts you need rather than the whole catalog; the minimal profile is for getting started.
What do the hooks run, and can I turn them off?
Node scripts (some Bash or Python): checks before and after commands and file writes, formatting, session summary. You choose the hook level during installation; you can scale it back later with environment variables. The no-hooks route: --profile minimal.
Does it work on Windows?
The core Node CLI runs on Windows, macOS and Linux; the README marks native Windows as supported with limitations, and there are open bug reports. The WSL route is supported as core.
Is ECC safe?
There is no security seal. No published advisory appears in GitHub Security Advisories (October 14, 2026). ECC's SECURITY.md only tells you to install from official sources and to treat hooks and MCPs as executable configuration.
Related guides
Sources
Not clear in the official sources: The full list of skills included in the minimal profile · the account requirement for AgentShield's --opus analysis · admin permission on a team account · whether #3279 and #3169 are resolved in 2.2.3 · Turkish support and local-currency pricing · OSV advisory status. Each is covered in the relevant section.