Everything Claude Code (ECC): What It Is, What 2.2.0 Changed, and How to Install It

What is everything-claude-code?

Everything Claude Code (ECC) is an MIT-licensed toolkit whose canonical GitHub repository is affaan-m/ECC. Its npm package is ecc-universal, while its Claude marketplace/plugin identifier is ecc@ecc. These names identify different distribution surfaces for the same project.

If you arrived through a search for “affaan-m everything-claude-code,” use those identifiers to distinguish the repository, the installer package, and the plugin. The version 2.2.0 README documents the toolkit and its installation options.

What does ECC add?

Version 2.2.0 contains 68 agents, 286 skills, and 94 command shims, alongside rules, hooks, memory, continuous learning, and installation tooling. Those are distribution-wide totals; they do not mean every supported coding tool receives identical capabilities.

The agents cover planning, review, build repair, security, architecture, and domain work. Skills span testing, research, documentation, frontend development, data, machine learning, and operations. AgentShield scans prompts, hooks, MCP configuration, permissions, secrets, and agent files.

Thinking of ECC as a Claude Code configuration collection is useful, but incomplete: the toolkit also includes installation tooling and support for other coding agents. For background on one of its main content types, see our Claude Code skills guide.

Is ECC free?

The open-source repository remains free, and ECC Pro is not required to install the OSS toolkit. The tagged README separately advertises a hosted ECC Pro + GitHub App for private repositories, starting at $19 per seat per month. That price belongs to the hosted offering, not the open-source installation.

What ECC 2.2.0 changed

ECC 2.2.0 was released on August 28, 2026, with the title “ECC 2.2.0: Guided Setup, Antigravity 2.0, and the Nasiko CLI Bridge.” The official release identifies guided setup as a central addition.

One guided installer for three harnesses

The new installer supports Claude Code, Codex, and Kimi. It checks every selected harness—the coding tool receiving ECC—before writing files.

Installation remains separate from provider setup. The installer does not install or authenticate provider CLIs, and provider model settings and authentication remain provider-controlled. Prepare those tools before running ECC setup.

Installation reliability and broader workflows

Version 2.2.0 also improves how installations track and preserve files:

• Cumulative ownership records survive repeated selective installs.
• OpenCode uses ~/.config/opencode.
• Legacy Codex cleanup preserves modified or untracked user files and requires ownership evidence by default.

Native Antigravity 2.0 installation targets .agents/{rules,workflows,skills,agents}. Workflow additions span Pi, Itô, agent evaluation, multi-model council, dev-team, living docs, secure terminal, TasteForge, and skill-comply.

The Nasiko bridge is experimental and opt-in. It supports one pinned Nasiko v0.1.0 CLI build with SHA-256-verified downloads. ECC does not operate Nasiko’s control plane or enable telemetry through this bridge.

Release assurance also covers the exact npm archive: it is hashed, tested on Linux, macOS, and Windows, published under a staging tag, and checked for registry integrity before latest moves. Version 2.1.0 remains the immediate rollback package.

How to install ECC 2.2.0

The npm package requires Node.js 18 or later. For the Claude plugin, you also need Claude Code CLI 2.1.0 or later. Check the installed Claude version in your terminal:

claude --version

If Claude Code still needs to be installed, start with our Claude Code installation guide. ECC’s installer expects the provider CLI to be present; it does not supply or authenticate it.

Start with the release-pinned installer

Run this command in a terminal to select the 2.2.0 npm package explicitly:

npx --yes ecc-universal@2.2.0 install --guided

The wizard previews destinations and requests confirmation. It supports --harness claude, --harness codex, --harness kimi, and --all-harnesses.

For a preview without changes, use the installer’s --dry-run option. Its --json option returns machine-readable output. The guided installer implementation documents these controls and the required choices for each harness.

There is one rollout qualification: the tagged README instructed users to check npm view ecc-universal version during npm propagation. The exact propagation completion time by August 31 is uncertain, so the release date alone does not establish when the registry’s default version changed.

Automate explicit choices

For noninteractive installation, provide the required choices and pass the installer’s --yes flag:

npx --yes ecc-universal@2.2.0 install --guided \
  --harness claude --harness codex --harness kimi \
  --claude-scope local --claude-hooks standard \
  --profile core --yes

This example selects all three harnesses, chooses Claude’s local scope and standard hook profile, and supplies the core content profile required for Kimi.

The two --yes flags serve different purposes. The first belongs to npx; the final flag authorizes noninteractive changes by the ECC installer. Keep those decisions explicit when adapting the command for automation.

Choose the right setup for each harness

ECC supports installing into Claude Code, Codex, and Kimi together, but their setup models differ. The 2.2.0 configuration skill distinguishes the following paths:

Claude Code: choose scope deliberately

Claude’s user scope applies globally for the user. The project scope shares configuration through repository settings, while local keeps it private to the project.

Choose based on who should receive the configuration: your user account, repository collaborators, or only your local project setup. Scope and hook profile are separate choices.

The available hook profiles are off, minimal, standard, and strict. The profile names alone should not substitute for reviewing the hooks you intend to enable. Our Claude Code hooks guide provides background for that review.

For a Claude-only installation, the native alternative is to run these commands inside Claude Code:

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

Codex: use its native trust controls

Codex has its own marketplace/plugin lifecycle, hook review, and explicit trust controls. Do not apply Claude’s scope names or four hook profiles to Codex.

Its native installation and verification commands are:

codex plugin marketplace add affaan-m/ECC
codex plugin add ecc@ecc --json
codex plugin list --json

The final command lists plugins in machine-readable form, giving you a concrete verification step after adding ECC.

Kimi: select project content

Kimi receives managed files under ./.kimi-code, and its guided installation requires a content profile. ECC lifecycle hooks are unsupported in this path.

Installing all three harnesses therefore means configuring three distinct integrations. It does not make their hook behavior or available components identical.

Updates, reconfiguration, and installation pitfalls

Choose one installation method per harness. Stacking the Claude plugin with a full manual installation can duplicate components; the same concern applies to combining Codex sync and marketplace installation.

If skills appear duplicated, check whether you have combined installation methods before adding more files. If rules appear missing from a Claude plugin installation, there is a separate explanation: Claude plugins do not distribute rules. Add the selected rule packs separately.

Updating and changing Claude scope

Existing Claude plugin installations can use /plugin update ecc. The Claude plugin wizard, ecc setup, can update an existing installation or migrate its scope.

During a scope migration, the wizard verifies the destination before removing the source. Afterward, reload with /reload-plugins or restart Claude Code. The setup implementation documents this behavior.

Keep package selection, plugin updates, and scope migration distinct when planning maintenance. The pinned npm command explicitly selects version 2.2.0; the plugin update command and setup wizard serve their respective plugin maintenance tasks.

Key takeaways

• ECC is affaan-m’s MIT-licensed toolkit, distributed through affaan-m/ECC, ecc-universal, and the ecc@ecc plugin identifier.
• Version 2.2.0 adds guided setup for Claude Code, Codex, and Kimi, with checks before files are written.
• Use npx --yes ecc-universal@2.2.0 install --guided for the release-pinned npm entry point; provider CLI installation and authentication remain separate.
• Claude, Codex, and Kimi use different scope, trust, and hook models. Distribution-wide component counts do not establish identical capabilities.
• Choose one installation method per harness, and add Claude rule packs separately when needed.

FAQ

Is Everything Claude Code free, or do I need ECC Pro?

Everything Claude Code’s open-source repository is free and MIT-licensed. ECC Pro is a separate hosted offering with a GitHub App for private repositories, advertised in the 2.2.0 README from $19 per seat per month; it is not required for OSS installation.

Can I install ECC in Claude Code, Codex, and Kimi simultaneously?

Yes, the 2.2.0 guided installer supports selecting all three harnesses. Claude uses a scoped plugin and hook profiles, Codex uses its native plugin lifecycle and trust controls, and Kimi receives project files without ECC lifecycle hooks.

Which Claude scope and hook profile should I choose?

Use user for configuration global to your user account, project for configuration shared through repository settings, or local for private project configuration. Hook profiles are off, minimal, standard, and strict; choose the profile separately from scope after reviewing the hooks you intend to enable.

Why are ECC skills duplicated or rules missing?

Combining the Claude plugin with a full manual installation, or Codex sync with marketplace installation, can duplicate components. Claude plugins do not distribute rules, so selected rule packs must be added separately.