TL;DR
- Everything Claude Code (ECC) is an open-source configuration framework for AI coding agents, now at 100K stars and 13K forks on GitHub.
- It ships with 28 specialized agents, 119 skills, and 60 commands, working across Claude Code, Cursor, Codex, and OpenCode from a single repo.
- Version 1.9.0, released in March 2026, adds a selective-install architecture, six new agents, and support for 12 language ecosystems.

Introduction
A community-built configuration system for AI coding agents has crossed 100,000 GitHub stars and shows no signs of slowing down. Everything Claude Code (ECC) provides is a structured layer of skills, rules, hooks, security scanning, and memory persistence that works across Claude Code, Cursor, Codex, and OpenCode. For teams seeking consistent, reliable output from AI coding tools, this repo has become the de facto starting point.
What Happened
Developer Affaan Mustafa's open-source project, born from winning an Anthropic hackathon in September 2025, released v1.9.0 in March 2026 with 212 commits covering selective install architecture, six new agents, 15+ new skills, and support for 12 language ecosystems. The repo now includes 28 specialized agents, 119 skills, 60 slash commands, and 768 total commits from 113 contributors. It has 13K forks and is actively developed daily.
Key Features
- Cross-platform agent configs: Ships ready-made configurations for Claude Code, Cursor (.cursor/), Codex (.codex/), and OpenCode (.opencode/) from a single repo. AGENTS.md at the root is read by all four tools.
- 28 specialized subagents: Dedicated agents for planning, TDD, security review, build error resolution, and language-specific code review across TypeScript, Python, Go, Rust, Java, Kotlin, and C++.
- Hook-based security enforcement: PreToolUse hooks block --no-verify git flags, detect secrets in prompts (patterns like sk-, ghp_, AKIA), and prevent agents from modifying linter configs instead of fixing code. A config protection hook intercepts writes to .eslintrc, biome.json, .ruff.toml, and similar files.
- AgentShield security scanner: A dedicated tool with 1,282 tests and 102 static analysis rules. The --opus flag runs three Claude Opus agents in a red-team/blue-team/auditor pipeline for adversarial analysis of your agent configuration.
- Selective install pipeline: Manifest-driven installation via install-plan.js and install-apply.js. Install only the languages and components you need. A SQLite state store tracks what is installed and supports incremental updates.
- Memory persistence and learning: Session lifecycle hooks automatically save and load context. A continuous learning system (v2) extracts patterns from sessions into reusable instincts with confidence scoring, import/export, and evolution into full skills.
Why It Matters
AI coding agents are powerful but inconsistent. Without structured rules, they skip tests, modify linter configs to pass checks, commit with --no-verify, and lose context between sessions. ECC treats this as an engineering problem, not a prompt engineering problem.
The project reflects a broader shift: developers are moving beyond ad hoc agent use toward repeatable, auditable workflows. Teams get shared rules across tools, security guardrails that block common agent misbehaviors, and a hook system that enforces TDD and code review without manual oversight. The selective install system means a Python shop does not inherit TypeScript overhead.
With 113 contributors and translations in seven languages, ECC has become a community standard for agent configuration, the .editorconfig equivalent for AI coding tools.
Example Use Case
A team running a Django REST API adds ECC with Python-specific rules:
This installs common rules (git workflow, testing, security) plus Python-specific patterns, Django skills, and the security scanner. When a developer uses Claude Code to add an authentication endpoint, the TDD agent enforces write-tests-first. The post:edit:format hook runs Black on saved files. If the agent tries to modify .ruff.toml to suppress a warning, the config protection hook blocks the edit and redirects it to fix the actual code. At session end, the memory persistence hook saves context so the next session picks up where this one left off.
Competitive Context
Claude Code is ECC's primary target, with full coverage: 28 agents, 60 commands, 34 rules, and 8 hook event types. Cursor receives 15 hook event types via a DRY adapter pattern that reuses Claude Code's hook scripts without duplicating them. According to the project's feature parity table, OpenCode supports 11 hook events and 6 native custom tools, more than Claude Code in those specific areas, but fewer total agents (12 vs. 28) and commands (31 vs. 60).
Codex support is instruction-based via AGENTS.md, since Codex does not yet offer Claude-style hook execution. The gap ECC fills is standardization: before this project, each tool required separate configuration with no shared format. ECC's AGENTS.md-at-root convention and cross-platform hook adapter give teams one config that deploys across all four tools.
Bottom Line
Everything Claude Code is the most complete open-source framework for making AI coding agents behave consistently across tools. If your team uses Claude Code, Cursor, or Codex and wants enforced testing, security guardrails, and persistent memory without having to build them yourself, this is the project to evaluate. The 100K stars suggest that many teams already have.
You've seen what's under the hood. Try the tool built around context, not just prompts.
Free tier available · VS Code extension · Takes 2 minutes
Written by

Molisha Shah
GTM and Customer Champion