ECC (Everything Claude Code) is an open-source plugin that transforms Claude Code from a standard AI assistant into a team of 68 specialized engineers: from system architects and developers to TDD testers and security audit specialists. With just two simple installation commands, you can orchestrate an entire engineering department working seamlessly in Vietnamese.

1. What is ECC and the 68 Specialized AI Agent Architecture
Normally, when using Claude Code, a single AI has to handle every stage: planning, writing code, running tests, and self-evaluating. As the context window fills up, the AI begins to hallucinate, generating patched code and easily overlooking critical security vulnerabilities.
ECC fundamentally solves this problem through a specialized division of labor model:
- 68 Independent Agents: Each agent handles a deep specialization (Planner, Coder, Tester, Security Reviewer, alongside language-specific experts for Go, Python, TypeScript, Rust…).
- 292 Domain Skills: Automatically integrates modern techniques such as Test-Driven Development (TDD), database optimization, responsive UI development, and data analysis.
- AgentShield & GateGuard Protection Layers: Automatically detects and intercepts dangerous commands (such as batch file deletion
rm -rfor exposing.envfiles) before they are executed on your computer.
ECC was developed by developer Affaan Mustafa (affaan-m) under the MIT license, completely free to use for both personal and enterprise commercial projects.
Supported Platform Compatibility Table
| AI Tool | Compatibility Level & Recommendations |
|---|---|
| Claude Code | Official platform, 100% support for agents, hooks, and slash commands. (Recommended) |
| Codex (OpenAI) | Supports standalone plugins and compatible configuration commands. |
| Cursor / OpenCode | Beta version support, includes full core agents and skills. |
| Gemini CLI / Kimi | Separate installer via npm wizard, serves basic tasks. |
2. Environment Preparation Before Installation
To ensure the integration process runs smoothly in just 5 minutes, please check the following prerequisites list:
- Claude Code CLI 2.1+: Open your Terminal and verify with the command
claude --version. - Git: Installed on your system to download the plugin (verify with
git --version). - Node.js 18+ LTS: Only required if you choose the npx wizard installation method (verify with
node --version). - Test Project: Prepare a Git repository with actual code to test the power of the agents.
The ECC repo itself is 100% free. However, to run Claude Code, you will need a Claude Pro account (around $20/month) or a Max plan / API key to provide context for the Claude model.
3. 2-Step Guide to Installing ECC in Claude Code
The entire installation process consists of just 2 commands executed directly within the Claude Code command-line interface:
Step 1: Register ECC Marketplace
Launch Claude Code in your project directory and paste the following command:
Step 2: Install the ecc@ecc plugin package
Proceed to paste the official installation command:
When Claude Code prompts for the installation scope, you should choose:
- user: Enables ECC across all projects on your machine (the best choice for individuals).
- project: Saves the configuration only within the current project to share it with your team via Git.
Choose only one single installation method (the /plugin command above is recommended). Never combine multiple installation methods at the same time to avoid duplicating hooks and wasting tokens.
Alternative: Install via npx wizard
If your environment has trouble with the /plugin command, you can run the automated installer from an external Terminal:
Installation for OpenAI Codex CLI
If you are using OpenAI’s Codex CLI tool, run the following two commands in your Terminal:
4. Four Core Stages: Plan to Code to Test to Security
The standard ECC workflow clearly separates 4 roles so that no agent excuses its own mistakes:
Establish architectural blueprints, divide modules, and define dependency boundaries before writing the first line of code.
Implement code precisely according to technical specifications without arbitrarily altering system logic.
Apply rigorous TDD standards and write test cases targeting edge cases prior to feature acceptance.
Scrutinize source code from a hacker’s perspective, detecting SQL injection, XSS, secret key leaks, and improper access controls.
Example orchestration command during a session:
5. Running a full end-to-end cycle on a real project
Let’s walk through the closed-loop workflow from idea to finished product with these hands-on steps:
- Initialize the plan: Type
/ecc:plan [your feature]. The Planner Agent will analyze the project structure and create a detailed plan file. - Review the design: Carefully review the proposed steps. If satisfied, instruct it to begin coding:
- Automated testing: Invoke the TDD specialist to verify the correctness of the functions:
Run comprehensive TDD tests, ensuring 100% of edge cases have unit tests

Chưa có bình luận nào. Hãy là người đầu tiên chia sẻ góc nhìn!