Tools· AI Assistance & Agent Building

everything-claude-code (ECC)

everything-claude-code (ECC) is an MIT-licensed meta-collection of skills, agents, slash commands, hooks and rules packs that standardizes agentic coding workflows across multiple AI coding harnesses.

automatingstructuringexecutableOpen Source

Source code

/plugin marketplace add https://github.com/affaan-m/ECC, then /plugin install ecc@ecc. Copy rules manually to ~/.claude/rules/ecc/ if needed.

Open provider

Description

ECC bundles several hundred skills for different domains (among others test-driven development, frontend, backend, security and machine learning), plus more than sixty specialized sub-agents for tasks such as review, planning, build and security audit, a larger number of slash commands as a transitional solution during the migration of older workflows to skills, event-driven hooks (for example at session start, file edit or before a tool call) and rules packs organized by programming language and domain. Built primarily for Claude Code, the repository also covers Cursor, OpenCode, Codex, Gemini, GitHub Copilot, Zed and Antigravity, according to the source.

Because the collection is broad, the maturity of individual packs varies: some skills and rules are well tested, others less so. Anyone using ECC is well advised to adopt individual packs deliberately rather than activating the entire collection unchecked, otherwise redundant or conflicting automations easily arise between several hooks and rules active at the same time.

Strengths

Cross-harness support

According to the repository, the collection works not only with Claude Code but also with Codex, Cursor, OpenCode, Gemini, Zed, GitHub Copilot and other coding harnesses.

Broad skill and agent base

As of version 2.0.0 the repository counts, per its changelog, 261 skills plus several dozen specialized sub-agents for areas such as review, planning, build and security audit.

Active ongoing development

The changelog documents regular, topically scoped releases from v1.2.0 through v2.0.0, including new language rules, additional harness integrations and a dedicated orchestrator family.

Ready-made hooks

Event-driven hooks for session start, file edits or tool calls can be adopted directly instead of writing custom hook scripts for formatting, linting or type checking.

Assessment

AI features

Instinct-based learning A continuous-learning system collects so-called instincts with confidence scoring plus import and export functionality, according to the changelog since version 1.2.0.
Memory Vault for context handoffs A local, portable Markdown format (ecc.memory.v1) stores project and team context so that different harnesses such as Claude, Codex or Hermes can read the same state, instead of copying transcripts manually.
Model routing According to the changelog, the NanoClaw v2 component routes requests by model and allows hot-loading skills during an active session.
Security scanning integration The /security-scan command wires the AgentShield tool directly into the workflow, according to the changelog.

Suitable for

Teams that want to build a reusable base of skills, agents and rules for multiple projects instead of writing every automation from scratch
Developers who work with several AI coding harnesses in parallel and are looking for a shared rule and skill base across all of them
Projects that want to adopt ready-made hooks for formatting, linting, type checking or build verification instead of writing their own hook scripts
Less suitable for Less suitable when only a single, very specific skill is needed, in that case copying out one pack deliberately is more worthwhile than the full collection

Limitations and notes

Uneven pack maturity Because the collection is very broad, individual skills and rules packs are tested to varying degrees. Deliberately selecting individual packs is more sensible than activating everything unchecked.
Memory Vault unreviewed According to the README, Memory Vault entries in the current release remain unreviewed and create-only throughout. Human review is required before content is promoted into governed project documentation, and recalled content must never be treated as an executable instruction.
ECC 2.0 core still alpha The Rust-based control-plane prototype in the ecc2/ folder is usable per the changelog but explicitly marked as alpha, not a general release.
Separate install for the Memory Vault Skill-only, minimal, manual and Claude plugin installs do not put the Memory Vault runtime on PATH, per the README. The ecc-universal npm package must be installed separately.
Separately billed add-on skills The Itô prediction-market skill pack requires its own API access, according to the changelog, and is not part of ECC Tools billing.

Quick start

Add the plugin marketplace in Claude Code: /plugin marketplace add https://github.com/affaan-m/ECC
Install the plugin: /plugin install ecc@ecc
For a different harness such as Kimi Code, set up via the install script instead: bash ./install.sh --target kimi --profile minimal
Verify the installation: npx ecc doctor --target kimi (adjust the harness name accordingly)
For the Memory Vault, additionally install the npm package and initialize the project: npm install -g ecc-universal, then ecc memory init --scope project

Tips

Before activating anything, select individual skill and rules packs deliberately instead of adopting the whole collection unchecked, to avoid conflicting hooks.
Rules packs are not picked up automatically through the plugin install, copy them manually to ~/.claude/rules/ecc/ if needed.
For cross-harness handoffs, use the Memory Vault instead of copying transcripts manually: ecc memory handoff --target <harness> --title "..." --body-file ./handoff.md writes a handoff, ecc memory search "<term>" --target-harness <harness> reads it back in the target system.
Run ecc memory doctor before sharing team memories to validate the vault.
Treat the Rust-based control-plane prototype in ecc2/ as alpha and do not use it in production.

Access

Repository: https://github.com/affaan-m/ECC (license: MIT for the core repository, individual packs may carry their own provenance and license notices in their respective folder). Installation via the Claude Code plugin marketplace: /plugin marketplace add https://github.com/affaan-m/ECC, then /plugin install ecc@ecc. Rules packs are not picked up automatically this way and must be copied manually to ~/.claude/rules/ecc/ if needed. We provide access to the source here only, no hosting of our own.