After Codex CLI, I Found ECC — The 199K★ Framework That Unites Every AI Coding Agent

TL;DR: After setting up Codex CLI with DeepSeek (my last post), I hit a new problem — every AI coding agent has its own config, skills, and rules. ECC solves this with one unified system across 20+ platforms. 199K★ on GitHub. Here's what I found.

---

The Problem I Didn't See Coming

Last week I wrote about giving Codex CLI superpowers with DeepSeek. It worked great.

Then I wanted to try Claude Code. Different config. Different skills format. Different rules syntax.

Then Cursor. Different everything.

Three agents. Three separate setups. Same frustration.

That's when I found ECC (198,874★ on GitHub) — a framework that treats every AI coding agent as a compatible harness rather than a separate ecosystem.

What ECC Does

ECC is the harness-native operator system for agentic work. Translation: one set of skills, rules, and configs that works across every major AI coding agent.

┌─────────────────────────────────────────┐
│           Your Skills & Rules           │
└────────────┬────────────┬───────────────┘
             │            │
     ┌───────┴────┐ ┌────┴───────┐
     │  ECC Core  │ │ AgentShield │
     └───────┬────┘ └────┬───────┘
             │            │
    ┌────────┴────────────┴────────┐
    │  20+ Agent Platforms         │
    │  Codex │ Claude │ Cursor    │
    │  Gemini │ Qwen │ OpenCode   │
    │  Zed │ Kiro │ Trae │ ...    │
    └─────────────────────────────┘

Write once. Run anywhere.

What's Inside (The Numbers)

Component	Count
⭐ GitHub Stars	198,874
🍴 Forks	30,500+
👥 Contributors	170+
🤖 Specialized Agents	63
📚 Unified Skills	249
⚙️ Legacy Commands	79
🛡️ Security Tests	1,282
📜 Security Rules	102
💰 ECC Pro	$19/seat/mo

How It Works

ECC organizes everything into 6 systems:

1. Agent Definitions (agents/)

63 pre-configured specialist agents. Each has its own persona, skills, rules, and hooks — but they're written in ECC's universal format.

2. Unified Skills (skills/)

249 skills in one format that works across all agents. Languages: Shell, TypeScript, Python, Go, Java, Perl, Markdown.

3. Cross-Platform Rules (rules/)

Write a rule once. It applies in Claude Code, Codex CLI, Cursor, Gemini, Qwen, and 15+ others.

4. Hooks System (hooks/)

Event-driven automation. PreToolUse hooks that trigger actions before the agent runs a tool. Think CI/CD for AI agents.

5. AgentShield Security

1,282 security tests, 102 rules. Catches dangerous operations before they happen. Open source and free.

6. MCP Configs (mcp-configs/)

Unified MCP (Model Context Protocol) server configs. Set up your tools once, share across all agents.

The Directory Structure

Here's what ECC adds to your project:

.agents/      → Universal agent definitions
.claude/      → Claude Code configs
.claude-plugin/ → Claude plugin
.codex/       → Codex CLI configs  
.cursor/      → Cursor configs
.gemini/      → Gemini CLI
.qwen/        → Qwen (Alibaba)
.kiro/        → Kiro
.opencode/    → OpenCode
.trae/        → Trae (ByteDance)
.zed/         → Zed editor
.vscode/      → VS Code

ECC manages ALL of these from one configuration. You don't touch individual directories.

Installing ECC

# One command:
npx ecc-universal

# Add security:
npx ecc-agentshield

# Initialize in existing project:
cd your-project
npx ecc-universal init

That's it. ECC auto-detects which agents you have installed and generates the right configs.

What I Actually Learned

1. The "Harness-Native" Concept Is Genius

ECC doesn't replace your agent. It wraps it. Your skills and rules become portable across any harness (Codex, Claude, Cursor, Gemini...). This is the right abstraction level — not replacing tools, but standardizing the interface between you and them.

2. Security Matters More Than Features

AgentShield is the most underrated part of ECC. 1,282 security tests that check whether a prompt or operation is safe. In a world where agents can delete files and run shell commands, this isn't optional.

3. The Ecosystem Is Bigger Than I Thought

ECC supports 20+ platforms. I knew about Codex, Claude, and Cursor. But Qwen? Kiro? Trae? There's a whole Chinese AI agent ecosystem I hadn't explored.

4. 199K Stars Didn't Come From Marketing

ECC earned its stars by solving a real pain. Every developer who uses multiple AI agents has felt this friction. ECC removes it.

ECC v2.0.0: What's New

The latest release (v2.0.0-rc.1) adds:

• Dashboard GUI — Visual management of agents, skills, and workflows
• Operator Mode — Production workflow orchestration
• Instinct-Based Learning — Auto-extracts patterns from agent conversations and evolves skills
• Improved Cross-Platform Sync — Real-time sync across multiple Agent harnesses

How It Connects to My Last Post

In my previous article, I showed how to break vendor lock-in by routing Codex CLI through a local shim.

ECC takes this further: once your agents can talk to any model, ECC makes them all work from the same playbook.

• Step 1: Free your agent from vendor lock (codex-shim)
• Step 2: Unify your agents under one system (ECC)
• Step 3: Secure and scale your agentic workflows

Two open source projects. One philosophy: tools should serve you, not the other way around.

Try It

npx ecc-universal

Resources:

• GitHub: github.com/affaan-m/ECC (199K★)
• ECC Pro: $19/seat/mo
• License: MIT (free) / Pro (paid)

---

Two posts, one week: breaking vendor lock-in, then unifying the ecosystem. The AI coding landscape is evolving fast. Better to ride the wave than fight it. 🌊