Web Analytics

everything-claude-code

⭐ 174096 stars English by affaan-m

Language: English | Português (Brasil) | 简体中文 | 繁體中文 | 日本語 | 한국어 | Türkçe

Everything Claude Code

Everything Claude Code — the performance system for AI agent harnesses

Stars Forks Contributors npm ecc-universal npm ecc-agentshield GitHub App Install License Shell TypeScript Python Go Java Perl Markdown

140K+ stars | 21K+ forks | 170+ contributors | 12+ language ecosystems | Anthropic Hackathon Winner

Language / 语言 / 語言 / Dil

English | Português (Brasil) | 简体中文 | 繁體中文 | 日本語 | 한국어 | Türkçe

The performance optimization system for AI agent harnesses. From an Anthropic hackathon winner.

Not just configs. A complete system: skills, instincts, memory optimization, continuous learning, security scanning, and research-first development. Production-ready agents, skills, hooks, rules, MCP configurations, and legacy command shims evolved over 10+ months of intensive daily use building real products.

Works across Claude Code, Codex, Cursor, OpenCode, Gemini, and other AI agent harnesses.

ECC v2.0.0-rc.1 adds the public Hermes operator story on top of that reusable layer: start with the Hermes setup guide, then review the rc.1 release notes and cross-harness architecture.

The Guides

This repo is the raw code only. The guides explain everything.

The Shorthand Guide to Everything Claude Code The Longform Guide to Everything Claude Code The Shorthand Guide to Everything Agentic Security
Shorthand Guide
Setup, foundations, philosophy. Read this first.		 Longform Guide
Token optimization, memory persistence, evals, parallelization.		 Security Guide
Attack vectors, sandboxing, sanitization, CVEs, AgentShield.

| Topic | What You'll Learn | |-------|-------------------| | Token Optimization | Model selection, system prompt slimming, background processes | | Memory Persistence | Hooks that save/load context across sessions automatically | | Continuous Learning | Auto-extract patterns from sessions into reusable skills | | Verification Loops | Checkpoint vs continuous evals, grader types, pass@k metrics | | Parallelization | Git worktrees, cascade method, when to scale instances | | Subagent Orchestration | The context problem, iterative retrieval pattern |

What's New

v2.0.0-rc.1 — Surface Refresh, Operator Workflows, and ECC 2.0 Alpha (Apr 2026)

v1.9.0 — Selective Install & Language Expansion (Mar 2026)

v1.8.0 — Harness Performance System (Mar 2026)

v1.7.0 — Cross-Platform Expansion & Presentation Builder (Feb 2026)

v1.6.0 — Codex CLI, AgentShield & Marketplace (Feb 2026)

v1.4.1 — Bug Fix (Feb 2026)

v1.4.0 — Multi-Language Rules, Installation Wizard & PM2 (Feb 2026)

v1.3.0 — OpenCode Plugin Support (Feb 2026)

v1.2.0 — Unified Commands & Skills (Feb 2026)

See the full changelog in Releases.

---

Quick Start

Get up and running in under 2 minutes:

Pick one path only

Most Claude Code users should use exactly one install path:

If you already layered multiple installs and things look duplicated, skip straight to Reset / Uninstall ECC.

Low-context / no-hooks path

If hooks feel too global or you only want ECC's rules, agents, commands, and core workflow skills, skip the plugin and use the minimal manual profile:

./install.sh --profile minimal --target claude

.\install.ps1 --profile minimal --target claude

or

npx ecc-install --profile minimal --target claude

This profile intentionally excludes hooks-runtime.

If you want the normal core profile but need hooks off, use:

./install.sh --profile core --without baseline:hooks --target claude

Add hooks later only if you want runtime enforcement:

./install.sh --target claude --modules hooks-runtime

Find the right components first

If you are not sure which ECC profile or component to install, ask the packaged advisor from any project:

npx ecc consult "security reviews" --target claude

It returns matching components, related profiles, and preview/install commands. Use the preview command before installing if you want to inspect the exact file plan.

Step 1: Install the Plugin (Recommended)

NOTE: The plugin is convenient, but the OSS installer below is still the most reliable path if your Claude Code build has trouble resolving self-hosted marketplace entries.

# Add marketplace
/plugin marketplace add https://github.com/affaan-m/everything-claude-code
Install plugin

/plugin install everything-claude-code@everything-claude-code

Naming + Migration Note

ECC now has three public identifiers, and they are not interchangeable:

This is intentional. Anthropic marketplace/plugin installs are keyed by a canonical plugin identifier, so ECC standardized on everything-claude-code@everything-claude-code to keep the listing name, /plugin install, /plugin list, and repo docs aligned to one public install surface. Older posts may still show the old short-form nickname; that shorthand is deprecated. Separately, the npm package stayed on ecc-universal, so npm installs and marketplace installs intentionally use different names.

Step 2: Install Rules (Required)

WARNING: Important: Claude Code plugins cannot distribute rules automatically.
>
If you already installed ECC via /plugin install, do not run ./install.sh --profile full, .\install.ps1 --profile full, or npx ecc-install --profile full afterward. The plugin already loads ECC skills, commands, and hooks. Running the full installer after a plugin install copies those same surfaces into your user directories and can create duplicate skills plus duplicate runtime behavior.
>
For plugin installs, manually copy only the rules/ directories you want under ~/.claude/rules/ecc/. Start with rules/common plus one language or framework pack you actually use. Do not copy every rules directory unless you explicitly want all of that context in Claude.
>
Use the full installer only when you are doing a fully manual ECC install instead of the plugin path.
>
If your local Claude setup was wiped or reset, that does not mean you need to repurchase ECC. Start with node scripts/ecc.js list-installed, then run node scripts/ecc.js doctor and node scripts/ecc.js repair before reinstalling anything. That usually restores ECC-managed files without rebuilding your setup. If the problem is account or marketplace access for ECC Tools, handle billing/account recovery separately.

# Clone the repo first
git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code
Install dependencies (pick your package manager)

npm install        # or: pnpm install | yarn install | bun install
Plugin install path: copy only ECC rules into an ECC-owned namespace

mkdir -p ~/.claude/rules/ecc
cp -R rules/common ~/.claude/rules/ecc/
cp -R rules/typescript ~/.claude/rules/ecc/
Fully manual ECC install path (use this instead of /plugin install)


./install.sh --profile full

# Windows PowerShell
Plugin install path: copy only ECC rules into an ECC-owned namespace

New-Item -ItemType Directory -Force -Path "$HOME/.claude/rules/ecc" | Out-Null
Copy-Item -Recurse rules/common "$HOME/.claude/rules/ecc/"
Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/ecc/"
Fully manual ECC install path (use this instead of /plugin install)


.\install.ps1 --profile full


npx ecc-install --profile full

For manual install instructions see the README in the rules/ folder. When copying rules manually, copy the whole language directory (for example rules/common or rules/golang), not the files inside it, so relative references keep working and filenames do not collide.

Fully manual install (Fallback)

Use this only if you are intentionally skipping the plugin path:

./install.sh --profile full

.\install.ps1 --profile full

or

npx ecc-install --profile full
If you choose this path, stop there. Do not also run /plugin install.

Reset / Uninstall ECC

If ECC feels duplicated, intrusive, or broken, do not keep reinstalling it on top of itself.

node scripts/uninstall.js --dry-run

Then remove ECC-managed files:

node scripts/uninstall.js
You can also use the lifecycle wrapper:

node scripts/ecc.js list-installed
node scripts/ecc.js doctor
node scripts/ecc.js repair
node scripts/ecc.js uninstall --dry-run

ECC only removes files recorded in its install-state. It will not delete unrelated files it did not install.

If you stacked methods, clean up in this order:

Step 3: Start Using

# Skills are the primary workflow surface.

Existing slash-style command names still work while ECC migrates off commands/.
Plugin install uses the canonical namespaced form

/everything-claude-code:plan "Add user authentication"
Manual install keeps the shorter slash form:


/plan "Add user authentication"
Check available commands

/plugin list everything-claude-code@everything-claude-code

That's it! You now have access to 48 agents, 182 skills, and 68 legacy command shims.

Dashboard GUI

Launch the desktop dashboard to visually explore ECC components:

npm run dashboard

or

python3 ./ecc_dashboard.py

Features:

Multi-model commands require additional setup

WARNING: multi-* commands are not covered by the base plugin/rules install above.
>
To use /multi-plan, /multi-execute, /multi-backend, /multi-frontend, and /multi-workflow, you must also install the ccg-workflow runtime.
>
Initialize it with npx ccg-workflow.
>
That runtime provides the external dependencies these commands expect, including:
- ~/.claude/bin/codeagent-wrapper
- ~/.claude/.ccg/prompts/*
>
Without ccg-workflow, these multi-* commands will not run correctly.

Cross-Platform Support

This plugin now fully supports Windows, macOS, and Linux, alongside tight integration across major IDEs (Cursor, OpenCode, Antigravity) and CLI harnesses. All hooks and scripts have been rewritten in Node.js for maximum compatibility.

Package Manager Detection

The plugin automatically detects your preferred package manager (npm, pnpm, yarn, or bun) with the following priority:

To set your preferred package manager:

# Via environment variable
export CLAUDE_PACKAGE_MANAGER=pnpm
Via global config

node scripts/setup-package-manager.js --global pnpm
Via project config

node scripts/setup-package-manager.js --project bun
Detect current setting

node scripts/setup-package-manager.js --detect

Or use the /setup-pm command in Claude Code.

Hook Runtime Controls

Use runtime flags to tune strictness or disable specific hooks temporarily:

# Hook strictness profile (default: standard)
export ECC_HOOK_PROFILE=standard
Comma-separated hook IDs to disable

export ECC_DISABLED_HOOKS="pre:bash:tmux-reminder,post:edit:typecheck"
Cap SessionStart additional context (default: 8000 chars)

export ECC_SESSION_START_MAX_CHARS=4000
Disable SessionStart additional context entirely for low-context/local-model setups

export ECC_SESSION_START_CONTEXT=off

What's Inside

This repo is a Claude Code plugin - install it directly or copy components manually.

everything-claude-code/
|-- .claude-plugin/   # Plugin and marketplace manifests
|   |-- plugin.json         # Plugin metadata and component paths
|   |-- marketplace.json    # Marketplace catalog for /plugin marketplace add
|
|-- agents/           # 36 specialized subagents for delegation
|   |-- planner.md           # Feature implementation planning
|   |-- architect.md         # System design decisions
|   |-- tdd-guide.md         # Test-driven development
|   |-- code-reviewer.md     # Quality and security review
|   |-- security-reviewer.md # Vulnerability analysis
|   |-- build-error-resolver.md
|   |-- e2e-runner.md        # Playwright E2E testing
|   |-- refactor-cleaner.md  # Dead code cleanup
|   |-- doc-updater.md       # Documentation sync
|   |-- docs-lookup.md       # Documentation/API lookup
|   |-- chief-of-staff.md    # Communication triage and drafts
|   |-- loop-operator.md     # Autonomous loop execution
|   |-- harness-optimizer.md # Harness config tuning
|   |-- cpp-reviewer.md      # C++ code review
|   |-- cpp-build-resolver.md # C++ build error resolution
|   |-- go-reviewer.md       # Go code review
|   |-- go-build-resolver.md # Go build error resolution
|   |-- python-reviewer.md   # Python code review
|   |-- database-reviewer.md # Database/Supabase review
|   |-- typescript-reviewer.md # TypeScript/JavaScript code review
|   |-- java-reviewer.md     # Java/Spring Boot code review
|   |-- java-build-resolver.md # Java/Maven/Gradle build errors
|   |-- kotlin-reviewer.md   # Kotlin/Android/KMP code review
|   |-- kotlin-build-resolver.md # Kotlin/Gradle build errors
|   |-- rust-reviewer.md     # Rust code review
|   |-- rust-build-resolver.md # Rust build error resolution
|   |-- pytorch-build-resolver.md # PyTorch/CUDA training errors
|
|-- skills/           # Workflow definitions and domain knowledge
|   |-- coding-standards/           # Language best practices
|   |-- clickhouse-io/              # ClickHouse analytics, queries, data engineering
|   |-- backend-patterns/           # API, database, caching patterns
|   |-- frontend-patterns/          # React, Next.js patterns
|   |-- frontend-slides/            # HTML slide decks and PPTX-to-web presentation workflows (NEW)
|   |-- article-writing/            # Long-form writing in a supplied voice without generic AI tone (NEW)
|   |-- content-engine/             # Multi-platform social content and repurposing workflows (NEW)
|   |-- market-research/            # Source-attributed market, competitor, and investor research (NEW)
|   |-- investor-materials/         # Pitch decks, one-pagers, memos, and financial models (NEW)
|   |-- investor-outreach/          # Personalized fundraising outreach and follow-up (NEW)
|   |-- continuous-learning/        # Legacy v1 Stop-hook pattern extraction
|   |-- continuous-learning-v2/     # Instinct-based learning with confidence scoring
|   |-- iterative-retrieval/        # Progressive context refinement for subagents
|   |-- strategic-compact/          # Manual compaction suggestions (Longform Guide)
|   |-- tdd-workflow/               # TDD methodology
|   |-- security-review/            # Security checklist
|   |-- eval-harness/               # Verification loop evaluation (Longform Guide)
|   |-- verification-loop/          # Continuous verification (Longform Guide)
|   |-- videodb/                   # Video and audio: ingest, search, edit, generate, stream (NEW)
|   |-- golang-patterns/            # Go idioms and best practices
|   |-- golang-testing/             # Go testing patterns, TDD, benchmarks
|   |-- cpp-coding-standards/         # C++ coding standards from C++ Core Guidelines (NEW)
|   |-- cpp-testing/                # C++ testing with GoogleTest, CMake/CTest (NEW)
|   |-- django-patterns/            # Django patterns, models, views (NEW)
|   |-- django-security/            # Django security best practices (NEW)
|   |-- django-tdd/                 # Django TDD workflow (NEW)
|   |-- django-verification/        # Django verification loops (NEW)
|   |-- laravel-patterns/           # Laravel architecture patterns (NEW)
|   |-- laravel-security/           # Laravel security best practices (NEW)
|   |-- laravel-tdd/                # Laravel TDD workflow (NEW)
|   |-- laravel-verification/       # Laravel verification loops (NEW)
|   |-- python-patterns/            # Python idioms and best practices (NEW)
|   |-- python-testing/             # Python testing with pytest (NEW)
|   |-- springboot-patterns/        # Java Spring Boot patterns (NEW)
|   |-- springboot-security/        # Spring Boot security (NEW)
|   |-- springboot-tdd/             # Spring Boot TDD (NEW)
|   |-- springboot-verification/    # Spring Boot verification (NEW)
|   |-- configure-ecc/              # Interactive installation wizard (NEW)
|   |-- security-scan/              # AgentShield security auditor integration (NEW)
|   |-- java-coding-standards/     # Java coding standards (NEW)
|   |-- jpa-patterns/              # JPA/Hibernate patterns (NEW)
|   |-- postgres-patterns/         # PostgreSQL optimization patterns (NEW)
|   |-- nutrient-document-processing/ # Document processing with Nutrient API (NEW)
|   |-- docs/examples/project-guidelines-template.md  # Template for project-specific skills
|   |-- database-migrations/         # Migration patterns (Prisma, Drizzle, Django, Go) (NEW)
|   |-- api-design/                  # REST API design, pagination, error responses (NEW)
|   |-- deployment-patterns/         # CI/CD, Docker, health checks, rollbacks (NEW)
|   |-- docker-patterns/            # Docker Compose, networking, volumes, container security (NEW)
|   |-- e2e-testing/                 # Playwright E2E patterns and Page Object Model (NEW)
|   |-- content-hash-cache-pattern/  # SHA-256 content hash caching for file processing (NEW)
|   |-- cost-aware-llm-pipeline/     # LLM cost optimization, model routing, budget tracking (NEW)
|   |-- regex-vs-llm-structured-text/ # Decision framework: regex vs LLM for text parsing (NEW)
|   |-- swift-actor-persistence/     # Thread-safe Swift data persistence with actors (NEW)
|   |-- swift-protocol-di-testing/   # Protocol-based DI for testable Swift code (NEW)
|   |-- search-first/               # Research-before-coding workflow (NEW)
|   |-- skill-stocktake/            # Audit skills and commands for quality (NEW)
|   |-- liquid-glass-design/         # iOS 26 Liquid Glass design system (NEW)
|   |-- foundation-models-on-device/ # Apple on-device LLM with FoundationModels (NEW)
|   |-- swift-concurrency-6-2/       # Swift 6.2 Approachable Concurrency (NEW)
|   |-- perl-patterns/             # Modern Perl 5.36+ idioms and best practices (NEW)
|   |-- perl-security/             # Perl security patterns, taint mode, safe I/O (NEW)
|   |-- perl-testing/              # Perl TDD with Test2::V0, prove, Devel::Cover (NEW)
|   |-- autonomous-loops/           # Autonomous loop patterns: sequential pipelines, PR loops, DAG orchestration (NEW)
|   |-- plankton-code-quality/      # Write-time code quality enforcement with Plankton hooks (NEW)
|
|-- commands/         # Maintained slash-entry compatibility; prefer skills/
|   |-- plan.md             # /plan - Implementation planning
|   |-- code-review.md      # /code-review - Quality review
|   |-- build-fix.md        # /build-fix - Fix build errors
|   |-- refactor-clean.md   # /refactor-clean - Dead code removal
|   |-- quality-gate.md     # /quality-gate - Verification gate
|   |-- learn.md            # /learn - Extract patterns mid-session (Longform Guide)
|   |-- learn-eval.md       # /learn-eval - Extract, evaluate, and save patterns (NEW)
|   |-- checkpoint.md       # /checkpoint - Save verification state (Longform Guide)
|   |-- setup-pm.md         # /setup-pm - Configure package manager
|   |-- go-review.md        # /go-review - Go code review (NEW)
|   |-- go-test.md          # /go-test - Go TDD workflow (NEW)
|   |-- go-build.md         # /go-build - Fix Go build errors (NEW)
|   |-- skill-create.md     # /skill-create - Generate skills from git history (NEW)
|   |-- instinct-status.md  # /instinct-status - View learned instincts (NEW)
|   |-- instinct-import.md  # /instinct-import - Import instincts (NEW)
|   |-- instinct-export.md  # /instinct-export - Export instincts (NEW)
|   |-- evolve.md           # /evolve - Cluster instincts into skills
|   |-- prune.md            # /prune - Delete expired pending instincts (NEW)
|   |-- pm2.md              # /pm2 - PM2 service lifecycle management (NEW)
|   |-- multi-plan.md       # /multi-plan - Multi-agent task decomposition (NEW)
|   |-- multi-execute.md    # /multi-execute - Orchestrated multi-agent workflows (NEW)
|   |-- multi-backend.md    # /multi-backend - Backend multi-service orchestration (NEW)
|   |-- multi-frontend.md   # /multi-frontend - Frontend multi-service orchestration (NEW)
|   |-- multi-workflow.md   # /multi-workflow - General multi-service workflows (NEW)
|   |-- sessions.md         # /sessions - Session history management
|   |-- test-coverage.md    # /test-coverage - Test coverage analysis
|   |-- update-docs.md      # /update-docs - Update documentation
|   |-- update-codemaps.md  # /update-codemaps - Update codemaps
|   |-- python-review.md    # /python-review - Python code review (NEW)
|-- legacy-command-shims/   # Opt-in archive for retired shims such as /tdd and /eval
|   |-- tdd.md              # /tdd - Prefer the tdd-workflow skill
|   |-- e2e.md              # /e2e - Prefer the e2e-testing skill
|   |-- eval.md             # /eval - Prefer the eval-harness skill
|   |-- verify.md           # /verify - Prefer the verification-loop skill
|   |-- orchestrate.md      # /orchestrate - Prefer dmux-workflows or multi-workflow
|
|-- rules/            # Always-follow guidelines (copy to ~/.claude/rules/ecc/)
|   |-- README.md            # Structure overview and installation guide
|   |-- common/              # Language-agnostic principles
|   |   |-- coding-style.md    # Immutability, file organization
|   |   |-- git-workflow.md    # Commit format, PR process
|   |   |-- testing.md         # TDD, 80% coverage requirement
|   |   |-- performance.md     # Model selection, context management
|   |   |-- patterns.md        # Design patterns, skeleton projects
|   |   |-- hooks.md           # Hook architecture, TodoWrite
|   |   |-- agents.md          # When to delegate to subagents
|   |   |-- security.md        # Mandatory security checks
|   |-- typescript/          # TypeScript/JavaScript specific
|   |-- python/              # Python specific
|   |-- golang/              # Go specific
|   |-- swift/               # Swift specific
|   |-- php/                 # PHP specific (NEW)
|
|-- hooks/            # Trigger-based automations
|   |-- README.md                 # Hook documentation, recipes, and customization guide
|   |-- hooks.json                # All hooks config (PreToolUse, PostToolUse, Stop, etc.)
|   |-- memory-persistence/       # Session lifecycle hooks (Longform Guide)
|   |-- strategic-compact/        # Compaction suggestions (Longform Guide)
|
|-- scripts/          # Cross-platform Node.js scripts (NEW)
|   |-- lib/                     # Shared utilities
|   |   |-- utils.js             # Cross-platform file/path/system utilities
|   |   |-- package-manager.js   # Package manager detection and selection
|   |-- hooks/                   # Hook implementations
|   |   |-- session-start.js     # Load context on session start
|   |   |-- session-end.js       # Save state on session end
|   |   |-- pre-compact.js       # Pre-compaction state saving
|   |   |-- suggest-compact.js   # Strategic compaction suggestions
|   |   |-- evaluate-session.js  # Extract patterns from sessions
|   |-- setup-package-manager.js # Interactive PM setup
|
|-- tests/            # Test suite (NEW)
|   |-- lib/                     # Library tests
|   |-- hooks/                   # Hook tests
|   |-- run-all.js               # Run all tests
|
|-- contexts/         # Dynamic system prompt injection contexts (Longform Guide)
|   |-- dev.md              # Development mode context
|   |-- review.md           # Code review mode context
|   |-- research.md         # Research/exploration mode context
|
|-- examples/         # Example configurations and sessions
|   |-- CLAUDE.md             # Example project-level config
|   |-- user-CLAUDE.md        # Example user-level config
|   |-- saas-nextjs-CLAUDE.md   # Real-world SaaS (Next.js + Supabase + Stripe)
|   |-- go-microservice-CLAUDE.md # Real-world Go microservice (gRPC + PostgreSQL)
|   |-- django-api-CLAUDE.md      # Real-world Django REST API (DRF + Celery)
|   |-- laravel-api-CLAUDE.md     # Real-world Laravel API (PostgreSQL + Redis) (NEW)
|   |-- rust-api-CLAUDE.md        # Real-world Rust API (Axum + SQLx + PostgreSQL) (NEW)
|
|-- mcp-configs/      # MCP server configurations
|   |-- mcp-servers.json    # GitHub, Supabase, Vercel, Railway, etc.
|
|-- ecc_dashboard.py  # Desktop GUI dashboard (Tkinter)
|
|-- assets/           # Assets for dashboard
|   |-- images/
|       |-- ecc-logo.png
|
|-- marketplace.json  # Self-hosted marketplace config (for /plugin marketplace add)

Ecosystem Tools

Skill Creator

Two ways to generate Claude Code skills from your repository:

#### Option A: Local Analysis (Built-in)

Use the /skill-create command for local analysis without external services:

/skill-create                    # Analyze current repo
/skill-create --instincts        # Also generate instincts for continuous-learning-v2

This analyzes your git history locally and generates SKILL.md files.

#### Option B: GitHub App (Advanced)

For advanced features (10k+ commits, auto-PRs, team sharing):

Install GitHub App | ecc.tools

# Comment on any issue:
/skill-creator analyze
Or auto-triggers on push to default branch

Both options create:

AgentShield — Security Auditor

Built at the Claude Code Hackathon (Cerebral Valley x Anthropic, Feb 2026). 1282 tests, 98% coverage, 102 static analysis rules.

Scan your Claude Code configuration for vulnerabilities, misconfigurations, and injection risks.

# Quick scan (no install needed)
npx ecc-agentshield scan
Auto-fix safe issues

npx ecc-agentshield scan --fix
Deep analysis with three Opus 4.6 agents

npx ecc-agentshield scan --opus --stream
Generate secure config from scratch

npx ecc-agentshield init

What it scans: CLAUDE.md, settings.json, MCP configs, hooks, agent definitions, and skills across 5 categories — secrets detection (14 patterns), permission auditing, hook injection analysis, MCP server risk profiling, and agent config review.

The --opus flag runs three Claude Opus 4.6 agents in a red-team/blue-team/auditor pipeline. The attacker finds exploit chains, the defender evaluates protections, and the auditor synthesizes both into a prioritized risk assessment. Adversarial reasoning, not just pattern matching.

Output formats: Terminal (color-graded A-F), JSON (CI pipelines), Markdown, HTML. Exit code 2 on critical findings for build gates.

Use /security-scan in Claude Code to run it, or add to CI with the GitHub Action.

GitHub | npm

Continuous Learning v2

The instinct-based learning system automatically learns your patterns:

/instinct-status        # Show learned instincts with confidence
/instinct-import  # Import instincts from others
/instinct-export        # Export your instincts for sharing
/evolve                 # Cluster related instincts into skills

See skills/continuous-learning-v2/ for full documentation. Keep continuous-learning/ only when you explicitly want the legacy v1 Stop-hook learned-skill flow.

Requirements

Claude Code CLI Version

Minimum version: v2.1.0 or later

This plugin requires Claude Code CLI v2.1.0+ due to changes in how the plugin system handles hooks.

Check your version: 

claude --version

Important: Hooks Auto-Loading Behavior

WARNING: For Contributors: Do NOT add a "hooks" field to .claude-plugin/plugin.json. This is enforced by a regression test.

Claude Code v2.1+ automatically loads hooks/hooks.json from any installed plugin by convention. Explicitly declaring it in plugin.json causes a duplicate detection error:

Duplicate hooks file detected: ./hooks/hooks.json resolves to already-loaded file

History: This has caused repeated fix/revert cycles in this repo (#29, #52, #103). The behavior changed between Claude Code versions, leading to confusion. We now have a regression test to prevent this from being reintroduced.

Installation

Option 1: Install as Plugin (Recommended)

The easiest way to use this repo - install as a Claude Code plugin:

# Add this repo as a marketplace
/plugin marketplace add https://github.com/affaan-m/everything-claude-code
Install the plugin

/plugin install everything-claude-code@everything-claude-code

Or add directly to your ~/.claude/settings.json:

{
  "extraKnownMarketplaces": {
    "ecc": {
      "source": {
        "source": "github",
        "repo": "affaan-m/everything-claude-code"
      }
    }
  },
  "enabledPlugins": {
    "everything-claude-code@everything-claude-code": true
  }
}
This gives you instant access to all commands, agents, skills, and hooks.

Note: The Claude Code plugin system does not support distributing rules via plugins (upstream limitation). You need to install rules manually:
> 
> # Clone the repo first
git clone https://github.com/affaan-m/everything-claude-code.git
>
# Option A: User-level rules (applies to all projects)
mkdir -p ~/.claude/rules/ecc
cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/
cp -r everything-claude-code/rules/typescript ~/.claude/rules/ecc/ # pick your stack
cp -r everything-claude-code/rules/python ~/.claude/rules/ecc/
cp -r everything-claude-code/rules/golang ~/.claude/rules/ecc/
cp -r everything-claude-code/rules/php ~/.claude/rules/ecc/
>
# Option B: Project-level rules (applies to current project only)
mkdir -p .claude/rules/ecc
cp -r everything-claude-code/rules/common .claude/rules/ecc/
cp -r everything-claude-code/rules/typescript .claude/rules/ecc/ # pick your stack
``

Option 2: Manual Installation

If you prefer manual control over what's installed:

bash

Clone the repo

git clone https://github.com/affaan-m/everything-claude-code.git

Copy agents to your Claude config

cp everything-claude-code/agents/*.md ~/.claude/agents/

Copy rules directories (common + language-specific)

mkdir -p ~/.claude/rules/ecc cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/ cp -r everything-claude-code/rules/typescript ~/.claude/rules/ecc/ # pick your stack cp -r everything-claude-code/rules/python ~/.claude/rules/ecc/ cp -r everything-claude-code/rules/golang ~/.claude/rules/ecc/ cp -r everything-claude-code/rules/php ~/.claude/rules/ecc/

Copy skills first (primary workflow surface)

Recommended (new users): core/general skills only

mkdir -p ~/.claude/skills/ecc cp -r everything-claude-code/.agents/skills/* ~/.claude/skills/ecc/ cp -r everything-claude-code/skills/search-first ~/.claude/skills/ecc/

Optional: add niche/framework-specific skills only when needed

for s in django-patterns django-tdd laravel-patterns springboot-patterns; do

cp -r everything-claude-code/skills/$s ~/.claude/skills/ecc/

done

Optional: keep maintained slash-command compatibility during migration

mkdir -p ~/.claude/commands cp everything-claude-code/commands/*.md ~/.claude/commands/

Retired shims live in legacy-command-shims/commands/.

Copy individual files from there only if you still need old names such as /tdd.


#### Install hooks
Do not copy the raw repo hooks/hooks.json into ~/.claude/settings.json or ~/.claude/hooks/hooks.json. That file is plugin/repo-oriented and is meant to be installed through the ECC installer or loaded as a plugin, so raw copying is not a supported manual install path.
Use the installer to install only the Claude hook runtime so command paths are rewritten correctly:
bash

macOS / Linux

bash ./install.sh --target claude --modules hooks-runtime
powershell

Windows PowerShell

pwsh -File .\install.ps1 --target claude --modules hooks-runtime 

That writes resolved hooks to ~/.claude/hooks/hooks.json and leaves any existing ~/.claude/settings.json untouched.
If you installed ECC via /plugin install, do not copy those hooks into settings.json. Claude Code v2.1+ already auto-loads plugin hooks/hooks.json, and duplicating them in settings.json causes duplicate execution and cross-platform hook conflicts.
Windows note: the Claude config directory is %USERPROFILE%\\.claude, not ~/claude.
#### Configure MCPs
Claude plugin installs intentionally do not auto-enable ECC's bundled MCP server definitions. This avoids overlong plugin MCP tool names on strict third-party gateways while keeping manual MCP setup available.
Use Claude Code's /mcp command or CLI-managed MCP setup for live Claude Code server changes. Use /mcp for Claude Code runtime disables; Claude Code persists those choices in ~/.claude.json.
For repo-local MCP access, copy desired MCP server definitions from mcp-configs/mcp-servers.json into a project-scoped .mcp.json.
If you already run your own copies of ECC-bundled MCPs, set:
bash export ECC_DISABLED_MCPS="github,context7,exa,playwright,sequential-thinking,memory" 

ECC-managed install and Codex sync flows will skip or remove those bundled servers instead of re-adding duplicates. ECC_DISABLED_MCPS is an ECC install/sync filter, not a live Claude Code toggle.
Important: Replace YOUR_*_HERE placeholders with your actual API keys.
Key Concepts
Agents
Subagents handle delegated tasks with limited scope. Example:
markdown
name: code-reviewer description: Reviews code for quality, security, and maintainability tools: ["Read", "Grep", "Glob", "Bash"] model: opus

You are a senior code reviewer... 



Skills
Skills are the primary workflow surface. They can be invoked directly, suggested automatically, and reused by agents. ECC still ships maintained commands/ during migration, while retired short-name shims live under legacy-command-shims/ for explicit opt-in only. New workflow development should land in skills/ first.
markdown

TDD Workflow

  • Define interfaces first
  • Write failing tests (RED)
  • Implement minimal code (GREEN)
  • Refactor (IMPROVE)
  • Verify 80%+ coverage


Hooks
Hooks trigger on tool events. Example - warn about console.log:
json { "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(ts|tsx|js|jsx)$\"", "hooks": [{ "type": "command", "command": "#!/bin/bash\ngrep -n 'console\\.log' \"$file_path\" && echo '[Hook] Remove console.log' >&2" }] } 


Rules
Rules are always-follow guidelines, organized into common/ (language-agnostic) + language-specific directories:
rules/ common/ # Universal principles (always install) typescript/ # TS/JS specific patterns and tools python/ # Python specific patterns and tools golang/ # Go specific patterns and tools swift/ # Swift specific patterns and tools php/ # PHP specific patterns and tools 

See rules/README.md for installation and structure details.
Which Agent Should I Use?
Not sure where to start? Use this quick reference. Skills are the canonical workflow surface; maintained slash entries stay available for command-first workflows.
| I want to... | Use this surface | Agent used |
|--------------|-----------------|------------|
| Plan a new feature | /everything-claude-code:plan "Add auth" | planner |
| Design system architecture | /everything-claude-code:plan + architect agent | architect |
| Write code with tests first | tdd-workflow skill | tdd-guide |
| Review code I just wrote | /code-review | code-reviewer |
| Fix a failing build | /build-fix | build-error-resolver |
| Run end-to-end tests | e2e-testing skill | e2e-runner |
| Find security vulnerabilities | /security-scan | security-reviewer |
| Remove dead code | /refactor-clean | refactor-cleaner |
| Update documentation | /update-docs | doc-updater |
| Review Go code | /go-review | go-reviewer |
| Review Python code | /python-review | python-reviewer |
| Review TypeScript/JavaScript code | (invoke typescript-reviewer directly) | typescript-reviewer |
| Audit database queries | (auto-delegated) | database-reviewer |
Common Workflows
Slash forms below are shown where they remain part of the maintained command surface. Retired short-name shims such as /tdd and /eval live in legacy-command-shims/ for explicit opt-in only.
Starting a new feature:
/everything-claude-code:plan "Add user authentication with OAuth" → planner creates implementation blueprint tdd-workflow skill → tdd-guide enforces write-tests-first /code-review → code-reviewer checks your work 
Fixing a bug:
tdd-workflow skill → tdd-guide: write a failing test that reproduces it → implement the fix, verify test passes /code-review → code-reviewer: catch regressions 

Preparing for production:
/security-scan → security-reviewer: OWASP Top 10 audit e2e-testing skill → e2e-runner: critical user flow tests /test-coverage → verify 80%+ coverage 


FAQ

How do I check which agents/commands are installed?
bash /plugin list everything-claude-code@everything-claude-code 

This shows all available agents, commands, and skills from the plugin.


My hooks aren't working / I see "Duplicate hooks file" errors
This is the most common issue. Do NOT add a "hooks" field to .claude-plugin/plugin.json. Claude Code v2.1+ automatically loads hooks/hooks.json from installed plugins. Explicitly declaring it causes duplicate detection errors. See #29, #52, #103.


Can I use ECC with Claude Code on a custom API endpoint or model gateway?
Yes. ECC does not hardcode Anthropic-hosted transport settings. It runs locally through Claude Code's normal CLI/plugin surface, so it works with:
  • Anthropic-hosted Claude Code
    • 

  • Official Claude Code gateway setups using ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN
    • 

  • Compatible custom endpoints that speak the Anthropic API Claude Code expects
Minimal example:
bash export ANTHROPIC_BASE_URL=https://your-gateway.example.com export ANTHROPIC_AUTH_TOKEN=your-token claude 

If your gateway remaps model names, configure that in Claude Code rather than in ECC. ECC's hooks, skills, commands, and rules are model-provider agnostic once the claude CLI is already working.
Official references:


My context window is shrinking / Claude is running out of context
Too many MCP servers eat your context. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k. SessionStart context is capped at 8000 characters by default; lower it with ECC_SESSION_START_MAX_CHARS=4000 or disable it with ECC_SESSION_START_CONTEXT=off for local-model or low-context setups.
Fix: Disable unused MCPs from Claude Code with /mcp. Claude Code writes those runtime choices to ~/.claude.json; .claude/settings.json and .claude/settings.local.json are not reliable toggles for already-loaded MCP servers.
Keep under 10 MCPs enabled and under 80 tools active.


Can I use only some components (e.g., just agents)?
Yes. Use Option 2 (manual installation) and copy only what you need:
bash

Just agents

cp everything-claude-code/agents/*.md ~/.claude/agents/

Just rules

mkdir -p ~/.claude/rules/ecc/ cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/ 

Each component is fully independent.


Does this work with Cursor / OpenCode / Codex / Antigravity?
Yes. ECC is cross-platform:

  • Cursor: Pre-translated configs in .cursor/. See Cursor IDE Support.
    • 

  • Gemini CLI: Experimental project-local support via .gemini/GEMINI.md and shared installer plumbing.
    • 

  • OpenCode: Full plugin support in .opencode/. See OpenCode Support.
    • 

  • Codex: First-class support for both macOS app and CLI, with adapter drift guards and SessionStart fallback. See PR #257.
    • 

  • Antigravity: Tightly integrated setup for workflows, skills, and flattened rules in .agent/. See Antigravity Guide.
    • 

  • Non-native harnesses: Manual fallback path for Grok and similar interfaces. See Manual Adaptation Guide.
    • 

  • Claude Code: Native — this is the primary target.
    • 


How do I contribute a new skill or agent?
See CONTRIBUTING.md. The short version:

  • Fork the repo
    • 

  • Create your skill in skills/your-skill-name/SKILL.md (with YAML frontmatter)
    • 

  • Or create an agent in agents/your-agent.md
    • 

  • Submit a PR with a clear description of what it does and when to use it
    • 

Running Tests
The plugin includes a comprehensive test suite:
bash

Run all tests

node tests/run-all.js

Run individual test files

node tests/lib/utils.test.js node tests/lib/package-manager.test.js node tests/hooks/hooks.test.js 


Contributing
Contributions are welcome and encouraged.
This repo is meant to be a community resource. If you have:

  • Useful agents or skills
    • 

  • Clever hooks
    • 

  • Better MCP configurations
    • 

  • Improved rules
Please contribute! See CONTRIBUTING.md for guidelines.
Ideas for Contributions
  • Language-specific skills (Rust, C#, Kotlin, Java) — Go, Python, Perl, Swift, and TypeScript already included
    • 

  • Framework-specific configs (Rails, FastAPI) — Django, NestJS, Spring Boot, and Laravel already included
    • 

  • DevOps agents (Kubernetes, Terraform, AWS, Docker)
    • 

  • Testing strategies (different frameworks, visual regression)
    • 

  • Domain-specific knowledge (ML, data engineering, mobile)
Community Ecosystem Notes
These are not bundled with ECC and are not audited by this repo, but they are worth knowing about if you are exploring the broader Claude Code skills ecosystem:
---
Cursor IDE Support
ECC provides Cursor IDE support with hooks, rules, agents, skills, commands, and MCP configs adapted for Cursor's project layout.
Quick Start (Cursor)
bash

macOS/Linux

./install.sh --target cursor typescript ./install.sh --target cursor python golang swift php
powershell

Windows PowerShell

.\install.ps1 --target cursor typescript .\install.ps1 --target cursor python golang swift php 


What's Included
| Component | Count | Details |
|-----------|-------|---------|
| Hook Events | 15 | sessionStart, beforeShellExecution, afterFileEdit, beforeMCPExecution, beforeSubmitPrompt, and 10 more |
| Hook Scripts | 16 | Thin Node.js scripts delegating to scripts/hooks/ via shared adapter |
| Rules | 34 | 9 common (alwaysApply) + 25 language-specific (TypeScript, Python, Go, Swift, PHP) |
| Agents | 48 | .cursor/agents/ecc-*.md when installed; prefixed to avoid collisions with user or marketplace agents |
| Skills | Shared + Bundled | .cursor/skills/ for translated additions |
| Commands | Shared | .cursor/commands/ if installed |
| MCP Config | Shared | .cursor/mcp.json if installed |
Cursor Loading Notes
ECC does not install root AGENTS.md into .cursor/. Cursor treats nested AGENTS.md files as directory context, so copying ECC's repo identity into a host project would pollute that project.
Cursor-native loading behavior can vary by Cursor build. ECC installs agents as .cursor/agents/ecc-*.md; if your Cursor build does not expose project agents, those files still work as explicit reference definitions instead of hidden global prompt context.
Hook Architecture (DRY Adapter Pattern)
Cursor has more hook events than Claude Code (20 vs 8). The .cursor/hooks/adapter.js module transforms Cursor's stdin JSON to Claude Code's format, allowing existing scripts/hooks/*.js to be reused without duplication.
Cursor stdin JSON → adapter.js → transforms → scripts/hooks/*.js (shared with Claude Code) 

Key hooks:

  • beforeShellExecution — Blocks dev servers outside tmux (exit 2), git push review
    • 

  • afterFileEdit — Auto-format + TypeScript check + console.log warning
    • 

  • beforeSubmitPrompt — Detects secrets (sk-, ghp_, AKIA patterns) in prompts
    • 

  • beforeTabFileRead — Blocks Tab from reading .env, .key, .pem files (exit 2)
    • 

  • beforeMCPExecution / afterMCPExecution — MCP audit logging
Rules Format
Cursor rules use YAML frontmatter with description, globs, and alwaysApply:
yaml
description: "TypeScript coding style extending common rules" globs: ["/.ts", "/.tsx", "/.js", "/.jsx"] alwaysApply: false 


Codex macOS App + CLI Support
ECC provides first-class Codex support for both the macOS app and CLI, with a reference configuration, Codex-specific AGENTS.md supplement, and shared skills.
Quick Start (Codex App + CLI)
bash

Run Codex CLI in the repo — AGENTS.md and .codex/ are auto-detected

codex

Automatic setup: sync ECC assets (AGENTS.md, skills, MCP servers) into ~/.codex

npm install && bash scripts/sync-ecc-to-codex.sh

or: pnpm install && bash scripts/sync-ecc-to-codex.sh

or: yarn install && bash scripts/sync-ecc-to-codex.sh

or: bun install && bash scripts/sync-ecc-to-codex.sh

Or manually: copy the reference config to your home directory

cp .codex/config.toml ~/.codex/config.toml 
The sync script safely merges ECC MCP servers into your existing ~/.codex/config.toml using an add-only strategy — it never removes or modifies your existing servers. Run with --dry-run to preview changes, or --update-mcp to force-refresh ECC servers to the latest recommended config.
For Context7, ECC uses the canonical Codex section name [mcp_servers.context7] while still launching the @upstash/context7-mcp package. If you already have a legacy [mcp_servers.context7-mcp] entry, --update-mcp migrates it to the canonical section name.
Codex macOS app:

  • Open this repository as your workspace.
    • 

  • The root AGENTS.md is auto-detected.
    • 

  • .codex/config.toml and .codex/agents/*.toml work best when kept project-local.
    • 

  • The reference .codex/config.toml intentionally does not pin model or model_provider, so Codex uses its own current default unless you override it.
    • 

  • Optional: copy .codex/config.toml to ~/.codex/config.toml for global defaults; keep the multi-agent role files project-local unless you also copy .codex/agents/.
What's Included
| Component | Count | Details |
|-----------|-------|---------|
| Config | 1 | .codex/config.toml — top-level approvals/sandbox/web_search, MCP servers, notifications, profiles |
| AGENTS.md | 2 | Root (universal) + .codex/AGENTS.md (Codex-specific supplement) |
| Skills | 32 | .agents/skills/ — SKILL.md + agents/openai.yaml per skill |
| MCP Servers | 6 | GitHub, Context7, Exa, Memory, Playwright, Sequential Thinking (7 with Supabase via --update-mcp sync) |
| Profiles | 2 | strict (read-only sandbox) and yolo (full auto-approve) |
| Agent Roles | 3 | .codex/agents/ — explorer, reviewer, docs-researcher |
Skills
Skills at .agents/skills/ are auto-loaded by Codex:
Canonical Anthropic skills such as claude-api, frontend-design, and skill-creator are intentionally not re-bundled here. Install those from anthropics/skills when you want the official versions.
| Skill | Description |
|-------|-------------|
| agent-introspection-debugging | Debug agent behavior, routing, and prompt boundaries |
| agent-sort | Sort agent catalogs and assignment surfaces |
| api-design | REST API design patterns |
| article-writing | Long-form writing from notes and voice references |
| backend-patterns | API design, database, caching |
| brand-voice | Source-derived writing style profiles from real content |
| bun-runtime | Bun as runtime, package manager, bundler, and test runner |
| coding-standards | Universal coding standards |
| content-engine | Platform-native social content and repurposing |
| crosspost | Multi-platform content distribution across X, LinkedIn, Threads |
| deep-research | Multi-source research with synthesis and source attribution |
| dmux-workflows | Multi-agent orchestration using tmux pane manager |
| documentation-lookup | Up-to-date library and framework docs via Context7 MCP |
| e2e-testing | Playwright E2E tests |
| eval-harness | Eval-driven development |
| everything-claude-code | Development conventions and patterns for the project |
| exa-search | Neural search via Exa MCP for web, code, company research |
| fal-ai-media | Unified media generation for images, video, and audio |
| frontend-patterns | React/Next.js patterns |
| frontend-slides | HTML presentations, PPTX conversion, visual style exploration |
| investor-materials | Decks, memos, models, and one-pagers |
| investor-outreach | Personalized outreach, follow-ups, and intro blurbs |
| market-research | Source-attributed market and competitor research |
| mcp-server-patterns | Build MCP servers with Node/TypeScript SDK |
| nextjs-turbopack | Next.js 16+ and Turbopack incremental bundling |
| product-capability | Translate product goals into scoped capability maps |
| security-review | Comprehensive security checklist |
| strategic-compact | Context management |
| tdd-workflow | Test-driven development with 80%+ coverage |
| verification-loop | Build, test, lint, typecheck, security |
| video-editing | AI-assisted video editing workflows with FFmpeg and Remotion |
| x-api | X/Twitter API integration for posting and analytics |
Key Limitation
Codex does not yet provide Claude-style hook execution parity. ECC enforcement there is instruction-based via AGENTS.md, optional model_instructions_file overrides, and sandbox/approval settings.
Multi-Agent Support
Current Codex builds support stable multi-agent workflows.
  • Enable features.multi_agent = true in .codex/config.toml
    • 

  • Define roles under [agents.]
    • 

  • Point each role at a file under .codex/agents/
    • 

  • Use /agent in the CLI to inspect or steer child agents
ECC ships three sample role configs:
| Role | Purpose |
|------|---------|
| explorer | Read-only codebase evidence gathering before edits |
| reviewer | Correctness, security, and missing-test review |
| docs_researcher | Documentation and API verification before release/docs changes |
OpenCode Support
ECC provides full OpenCode support including plugins and hooks.
Quick Start
bash

Install OpenCode

npm install -g opencode

Run in the repository root

opencode 

The configuration is automatically detected from .opencode/opencode.json.
Feature Parity
| Feature | Claude Code | OpenCode | Status |
|---------|-------------|----------|--------|
| Agents | PASS: 48 agents | PASS: 12 agents | Claude Code leads |
| Commands | PASS: 68 commands | PASS: 31 commands | Claude Code leads |
| Skills | PASS: 182 skills | PASS: 37 skills | Claude Code leads |
| Hooks | PASS: 8 event types | PASS: 11 events | OpenCode has more! |
| Rules | PASS: 29 rules | PASS: 13 instructions | Claude Code leads |
| MCP Servers | PASS: 14 servers | PASS: Full | Full parity |
| Custom Tools | PASS: Via hooks | PASS: 6 native tools | OpenCode is better |
Hook Support via Plugins
OpenCode's plugin system is MORE sophisticated than Claude Code with 20+ event types:
| Claude Code Hook | OpenCode Plugin Event |
|-----------------|----------------------|
| PreToolUse | tool.execute.before |
| PostToolUse | tool.execute.after |
| Stop | session.idle |
| SessionStart | session.created |
| SessionEnd | session.deleted |
Additional OpenCode events: file.edited, file.watcher.updated, message.updated, lsp.client.diagnostics, tui.toast.show, and more.
Maintained Slash Entries
| Command | Description |
|---------|-------------|
| /plan | Create implementation plan |
| /code-review | Review code changes |
| /build-fix | Fix build errors |
| /refactor-clean | Remove dead code |
| /learn | Extract patterns from session |
| /checkpoint | Save verification state |
| /quality-gate | Run the maintained verification gate |
| /update-docs | Update documentation |
| /update-codemaps | Update codemaps |
| /test-coverage | Analyze coverage |
| /go-review | Go code review |
| /go-test | Go TDD workflow |
| /go-build | Fix Go build errors |
| /python-review | Python code review (PEP 8, type hints, security) |
| /multi-plan | Multi-model collaborative planning |
| /multi-execute | Multi-model collaborative execution |
| /multi-backend | Backend-focused multi-model workflow |
| /multi-frontend | Frontend-focused multi-model workflow |
| /multi-workflow | Full multi-model development workflow |
| /pm2 | Auto-generate PM2 service commands |
| /sessions | Manage session history |
| /skill-create | Generate skills from git |
| /instinct-status | View learned instincts |
| /instinct-import | Import instincts |
| /instinct-export | Export instincts |
| /evolve | Cluster instincts into skills |
| /promote | Promote project instincts to global scope |
| /projects | List known projects and instinct stats |
| /prune | Delete expired pending instincts (30d TTL) |
| /learn-eval | Extract and evaluate patterns before saving |
| /setup-pm | Configure package manager |
| /harness-audit | Audit harness reliability, eval readiness, and risk posture |
| /loop-start | Start controlled agentic loop execution pattern |
| /loop-status | Inspect active loop status and checkpoints |
| /quality-gate | Run quality gate checks for paths or entire repo |
| /model-route | Route tasks to models by complexity and budget |
Plugin Installation
Option 1: Use directly
bash cd everything-claude-code opencode 

Option 2: Install as npm package
bash npm install ecc-universal 
Then add to your opencode.json:
json { "plugin": ["ecc-universal"] } 
That npm plugin entry enables ECC's published OpenCode plugin module (hooks/events and plugin tools).  
It does not automatically add ECC's full command/agent/instruction catalog to your project config.  
For the full ECC OpenCode setup, either:  

  • run OpenCode inside this repository, or  
    • 

  • copy the bundled .opencode/ config assets into your project and wire the instructions, agent, and command entries in opencode.json  
Documentation  
  • Migration Guide: .opencode/MIGRATION.md  
    • 

  • OpenCode Plugin README: .opencode/README.md  
    • 

  • Consolidated Rules: .opencode/instructions/INSTRUCTIONS.md  
    • 

  • LLM Documentation: llms.txt (complete OpenCode docs for LLMs)  
---  
Cross-Tool Feature Parity  
ECC is the first plugin to maximize every major AI coding tool. Here's how each harness compares:  
| Feature | Claude Code | Cursor IDE | Codex CLI | OpenCode |  
|---------|------------|------------|-----------|----------|  
| Agents | 48 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 |  
| Commands | 68 | Shared | Instruction-based | 31 |  
| Skills | 182 | Shared | 10 (native format) | 37 |  
| Hook Events | 8 types | 15 types | None yet | 11 types |  
| Hook Scripts | 20+ scripts | 16 scripts (DRY adapter) | N/A | Plugin hooks |  
| Rules | 34 (common + lang) | 34 (YAML frontmatter) | Instruction-based | 13 instructions |  
| Custom Tools | Via hooks | Via hooks | N/A | 6 native tools |  
| MCP Servers | 14 | Shared (mcp.json) | 7 (auto-merged via TOML parser) | Full |  
| Config Format | settings.json | hooks.json + rules/ | config.toml | opencode.json |  
| Context File | CLAUDE.md + AGENTS.md | AGENTS.md | AGENTS.md | AGENTS.md |  
| Secret Detection | Hook-based | beforeSubmitPrompt hook | Sandbox-based | Hook-based |  
| Auto-Format | PostToolUse hook | afterFileEdit hook | N/A | file.edited hook |  
| Version | Plugin | Plugin | Reference config | 2.0.0-rc.1 |  
Key architectural decisions:  

  • AGENTS.md at root is the universal cross-tool file (read by all 4 tools)  
    • 

  • DRY adapter pattern lets Cursor reuse Claude Code's hook scripts without duplication  
  • Skills format (SKILL.md with YAML frontmatter) works across Claude Code, Codex, and OpenCode
    • 

  • Codex's lack of hooks is compensated by AGENTS.md, optional model_instructions_file overrides, and sandbox permissions
---
Background
I've been using Claude Code since the experimental rollout. Won the Anthropic x Forum Ventures hackathon in Sep 2025 with @DRodriguezFX — built zenith.chat entirely using Claude Code.
These configs are battle-tested across multiple production applications.
Token Optimization
Claude Code usage can be expensive if you don't manage token consumption. These settings significantly reduce costs without sacrificing quality.
Recommended Settings
Add to ~/.claude/settings.json:
json { "model": "sonnet", "env": { "MAX_THINKING_TOKENS": "10000", "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50" } } 
| Setting | Default | Recommended | Impact |
|---------|---------|-------------|--------|
| model | opus | sonnet | ~60% cost reduction; handles 80%+ of coding tasks |
| MAX_THINKING_TOKENS | 31,999 | 10,000 | ~70% reduction in hidden thinking cost per request |
| CLAUDE_AUTOCOMPACT_PCT_OVERRIDE | 95 | 50 | Compacts earlier — better quality in long sessions |
Switch to Opus only when you need deep architectural reasoning:
/model opus 


Daily Workflow Commands
| Command | When to Use |
|---------|-------------|
| /model sonnet | Default for most tasks |
| /model opus | Complex architecture, debugging, deep reasoning |
| /clear | Between unrelated tasks (free, instant reset) |
| /compact | At logical task breakpoints (research done, milestone complete) |
| /cost | Monitor token spending during session |
Strategic Compaction
The strategic-compact skill (included in this plugin) suggests /compact at logical breakpoints instead of relying on auto-compaction at 95% context. See skills/strategic-compact/SKILL.md for the full decision guide.
When to compact:

  • After research/exploration, before implementation
    • 

  • After completing a milestone, before starting the next
    • 

  • After debugging, before continuing feature work
    • 

  • After a failed approach, before trying a new one
When NOT to compact:

  • Mid-implementation (you'll lose variable names, file paths, partial state)
Context Window Management
Critical: Don't enable all MCPs at once. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k.
  • Keep under 10 MCPs enabled per project
    • 

  • Keep under 80 tools active
    • 

  • Use /mcp to disable unused Claude Code MCP servers; those runtime choices persist in ~/.claude.json
    • 

  • Use ECC_DISABLED_MCPS only to filter ECC-generated MCP configs during install/sync flows
Agent Teams Cost Warning
Agent Teams spawns multiple context windows. Each teammate consumes tokens independently. Only use for tasks where parallelism provides clear value (multi-module work, parallel reviews). For simple sequential tasks, subagents are more token-efficient.
WARNING: Important Notes
Token Optimization
Hitting daily limits? See the Token Optimization Guide for recommended settings and workflow tips.
Quick wins:
json // ~/.claude/settings.json { "model": "sonnet", "env": { "MAX_THINKING_TOKENS": "10000", "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50", "CLAUDE_CODE_SUBAGENT_MODEL": "haiku" } } `

Use /clear between unrelated tasks, /compact at logical breakpoints, and /cost` to monitor spending.

Customization

These configs work for my workflow. You should:

---

Community Projects

Projects built on or inspired by Everything Claude Code:

| Project | Description | |---------|-------------| | EVC | Marketing agent workspace — 42 commands for content operators, brand governance, and multi-channel publishing. Visual overview. |

Built something with ECC? Open a PR to add it here.

Sponsors

This project is free and open source. Sponsors help keep it maintained and growing.

Become a Sponsor | Sponsor Tiers | Sponsorship Program

Star History

Star History Chart

Links

---

License

MIT - Use freely, modify as needed, contribute back if you can.

Star this repo if it helps. Read both guides. Build something great.

--- Tranlated By Open Ai Tx | Last indexed: 2026-05-06 ---

Original README: View on GitHub

Translated by OpenAiTx | Last updated: 2026-05-06