Introduction
Every developer who has used Claude Code, Codex, Cursor, or any AI coding agent knows the frustration: great potential, but inconsistent output, runaway token costs, no security awareness, and zero continuity between sessions. You spend hours re-explaining context, and your best ideas get lost when the conversation resets.
**Everything Claude Code **(ECC) — currently the fastest-growing open-source developer project on GitHub with 178,000+ stars, 27,400 forks, and contributions from 170+ developers — was built to solve exactly these problems. Created by affaan-m, winner of an Anthropic Hackathon, ECC started as a small configuration pack and has evolved into a complete agent harness performance optimization system spanning 12 language ecosystems, 48 specialized agents, 182 workflow skills, and 68 legacy command shims.
Unlike simple prompt templates, ECC is an installed system — a Claude Code plugin with hooks, rules, skills, commands, agents, and a desktop dashboard GUI. It works across Claude Code, Codex, Cursor, OpenCode, Gemini, Antigravity, and more. After 10+ months of intensive daily use building real products, ECC has proven itself at scale.
What Makes Everything Claude Code Different
1. Complete System, Not Just Prompts
Most “Claude Code tips” repos are just collections of prompts and .md files you copy-paste. ECC takes a fundamentally different approach:
- Plugin Architecture: Install via
/plugin install everything-claude-code@everything-claude-codeinto Claude Code’s marketplace, or use the manual installer (install.sh --profile full) - Hook Runtime: Session-start and session-end hooks that automatically save and restore context, summarize conversations, and enforce coding standards
- Rules Engine: Language-specific rule sets (TypeScript, Python, Go, Java, Kotlin, Rust, C++, PHP, Perl, Swift, Dart, and common standards) organized under
rules/with relative-reference preservation - Skills Library: 182 pre-built workflow definitions covering TDD, security reviews, deployments, Docker patterns, E2E testing, and domain-specific knowledge (Django, Laravel, Spring Boot, ClickHouse, etc.)
- Agents: 48 specialized subagents for delegation — from
plannerandarchitectto language-specific reviewers (python-reviewer,go-reviewer,java-build-resolver) and operational operators (loop-operator,harness-optimizer,chief-of-staff)
2. Token Optimization That Actually Works
One of ECC’s most impactful features is systematic token reduction. By slimming system prompts, managing background processes intelligently, and using strategic compacting techniques, users report 30–60% reduction in token usage without sacrificing output quality.
The key innovations:
- Model Selection Routing: Smart routing based on task complexity — lightweight models for simple tasks, premium models only when needed
- Session Context Management: Automatic compaction suggestions, checkpoint-based state saving, and progressive context refinement for subagents
- Selective Rule Loading: Only load language/framework rules you actually use, reducing unnecessary model context window bloat
3. AgentShield Security Integration
Security isn’t an afterthought in ECC — it’s baked into the workflow. The AgentShield integration provides:
- Real-time Security Scanning: Run
/security-scandirectly from Claude Code to audit your entire codebase - 102 Security Rules: Covering OWASP Top 10, common vulnerability patterns, dependency scanning, and input validation checks
- 1,282 Tests: Comprehensive test suite validating all security rules against known attack vectors
- Sandboxed Execution: Hooks can be run in sandboxed mode with strict permission boundaries
# Quick security scan of your current project
/security-scan
# Full security audit with detailed report
/security-scan --full
This makes ECC not just a productivity tool, but a production-grade security gateway that catches vulnerabilities before they reach your CI pipeline. Compare this to Chrome DevTools MCP which focuses on browser automation, or Anthropic’s Financial Services AI Agents which handles financial workflows — ECC sits right at the intersection where development meets security.
4. Cross-Harness Support
Perhaps the most practical feature for teams: ECC works across multiple AI coding platforms simultaneously. Install once, benefit everywhere:
| Platform | Support Level | Key Features |
|---|---|---|
| Claude Code | Full | Plugin, hooks, skills, commands, dashboard |
| **Codex **(CLI) | Full | AGENTS.md-based setup, /codex-setup command |
| **Codex **(App) | Full | Direct installation targeting |
| Cursor | Full | Native Cursor hook + MCP configuration |
| OpenCode | Full | Plugin system with 20+ event types, custom tools |
| Gemini | Full | Gemini-specific install target and rules |
| Antigravity IDE | Supported | PowerShell installer and IDE integration |
This cross-harness parity means teams can standardize their AI development practices regardless of which tool individual developers prefer.
Core Components Deep Dive
The Agent System (48 Specialized Agents)
ECC doesn’t rely on a single monolithic prompt. Instead, it deploys 48 specialized agents designed for specific tasks:
- Planning & Architecture:
planner,architect— Break down features into implementation plans, make system design decisions - Code Quality:
code-reviewer,tdd-guide,refactor-cleaner— Review changes, enforce TDD methodology, clean dead code - Security:
security-reviewer,database-reviewer— Analyze vulnerabilities, review database schemas and migrations - Language-Specific Reviewers:
python-reviewer,typescript-reviewer,java-reviewer,go-reviewer,rust-reviewer,cpp-reviewer,kotlin-reviewer,swift-reviewer - Build Error Resolvers:
build-error-resolver,java-build-resolver,pytorch-build-resolver— Fix compilation errors automatically - Operational:
loop-operator(autonomous loop execution),harness-optimizer(tune your agent config),e2e-runner(Playwright testing)
Each agent is a focused .md file with clear instructions, examples, and constraints. You invoke them with slash commands:
# Ask the planner to break down a feature
/plan "Add user authentication with OAuth2"
# Delegate code review to a specialist
/code-review .
# Get a security analysis
/security-review src/
Skills Workflow (182 Pre-Built Workflows)
Skills are the primary workflow surface in ECC. Each skill is a structured markdown document containing:
- Prerequisites: Required setup steps and dependencies
- Execution Steps: Numbered procedures with exact commands
- Decision Points: Conditional logic based on your environment
- Verification: How to confirm the workflow completed successfully
- Edge Cases: Common pitfalls and fallback strategies
Notable skills include:
tdd-workflow: Red-Green-Refactor methodology with pytest, Jest, and Playwright integrationsdeployment-patterns: CI/CD pipelines, Docker Compose, health checks, zero-downtime rollbacksdocker-patterns: Container networking, volume management, container security hardeningeval-harness: Checkpoint vs continuous evaluations, grader types, pass@k metricsverification-loop: Continuous verification gates for production deploymentscontinuous-learning-v2: Instinct-based learning with confidence scoring — your agents evolve over timecost-aware-llm-pipeline: Budget tracking, model routing, and cost optimizationmarket-research: Source-attributed competitor and market analysisinvestor-materials: Pitch decks, financial models, and fundraising outreach templates
For comparison, projects like Rowboat AI focus primarily on memory management, while ECC’s skills cover the entire software development lifecycle — from planning through deployment and beyond.
The Desktop Dashboard GUI
ECC v2.0 introduced a native Tkinter-based desktop application (ecc_dashboard.py or npm run dashboard) providing visual exploration of all components:
- Tabbed Interface: Switch between Agents, Skills, Commands, Rules, and Settings
- Search & Filter: Find any component instantly across the entire catalog
- Dark/Light Theme Toggle: Customize your workspace appearance
- Font Customization: Adjust family and size for comfortable reading
- Catalog Counts: Real-time visibility into your installed components (currently 48 agents, 182 skills, 68 legacy shims)
# Launch the dashboard
npm run dashboard
# Or use the Python version directly
python3 ./ecc_dashboard.py
Installation Guide
ECC offers multiple installation paths. Choose one only — stacking installations creates duplicate skills and broken behavior.
Recommended: Plugin Installation (2 minutes)
The easiest way to get started with ECC:
# In Claude Code, add the marketplace
/plugin marketplace add https://github.com/affaan-m/everything-claude-code
# Install the plugin
/plugin install everything-claude-code@everything-claude-code
# Copy rules you want into an ECC namespace
mkdir -p ~/.claude/rules/ecc
cp -R rules/common ~/.claude/rules/ecc/
cp -R rules/typescript ~/.claude/rules/ecc/ # Add your language-specific rules
That’s it. You now have access to all 48 agents, 182 skills, and 68 command shims.
Manual Installation (Fine-Grained Control)
For advanced users who want maximum control:
git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code
# Install dependencies
npm install # or: pnpm install | yarn install | bun install
# Full profile installation
./install.sh --profile full
Minimal Profile (Low-Context / No-Hooks)
If you only want rules and agents without runtime hooks:
./install.sh --profile minimal --target claude
Or with npm:
npx ecc-install --profile minimal --target claude
Package Manager Detection
ECC automatically detects your preferred package manager (npm, pnpm, yarn, bun):
# Set your preference globally
node scripts/setup-package-manager.js --global pnpm
# Detect current setting
node scripts/setup-package-manager.js --detect
Real-World Use Cases
Use Case 1: Solo Developer Building a SaaS
A solo founder building a React/Python API SaaS can leverage ECC to multiply their productivity:
- Planning Phase: Use the
planneragent to create a detailed feature roadmap - Development: Invoke
tdd-workflowskill for each feature, ensuring tests are written first - Integration: Apply
docker-patternsskill for consistent local development environments - Security: Run
AgentShieldscans weekly before deployments - Monitoring: Use
harness-optimizerto continuously tune token usage and response quality
Result: A solo developer shipping what previously required a team of three.
Use Case 2: Enterprise Development Team
An enterprise team adopting AI coding assistants faces unique challenges:
- Standardization: Deploy ECC rulesets across all 50 engineers for consistent code quality
- Security Compliance: Built-in AgentShield passes SOC2 audit requirements for code scanning
- Onboarding: New hires get immediate access to organizational patterns via shared skills
- Cost Control:
cost-aware-llm-pipelineskill tracks per-developer spending and optimizes model selection - Cross-Platform Consistency: Same ECC instance works whether developers use Cursor, Claude Code, or OpenCode
This aligns with approaches discussed in Production Engineering Skills for AI Coding Agents and builds on the principles outlined in the Hermes Agent self-improving documentation.
Use Case 3: Research & Startup Due Diligence
ECC’s market-research and investor-materials skills transform how startups approach investor preparation:
- Generate source-attributed market analysis reports
- Create professional pitch decks with LaTeX/PPTX conversion
- Build financial models with industry-standard templates
- Draft personalized investor outreach emails
Compare this to specialized tools like AI Trader for crypto trading or Pageindex for RAG pipelines — ECC covers the broader business intelligence spectrum.
Comparison with Alternatives
ECC vs Standard Claude Code Setup
| Feature | Standard Claude Code | With ECC |
|---|---|---|
| Token efficiency | Baseline | 30-60% reduction |
| Security scanning | None built-in | AgentShield (102 rules) |
| Session memory | Lost on reset | Auto-save/restore via hooks |
| Code quality gates | None | TDD + review + verification loops |
| Cross-platform | Single harness | 7+ platforms supported |
| Learning system | Static prompts | Continuous learning with confidence scoring |
| Dashboard | Terminal only | Desktop GUI |
ECC vs Agent Skills (addyosmani)
Both are top-tier open-source agent enhancement systems, but with different focuses:
- Agent Skills focuses on engineering practices (spec-driven development, incremental implementation, test-driven development)
- ECC focuses on agent harness performance (token optimization, hook reliability, session management, security)
- They complement each other well — many users install both
ECC vs Free Coding Resources
Projects like free-llm-api-resources help reduce API costs, while ECC reduces token consumption within your existing API budget. Together, they can cut total AI coding costs by 50-70%.
Getting Started Checklist
Here’s your path from zero to productive with ECC:
- [ ] Install ECC: Follow the plugin installation guide above
- [ ] Select Your Rules: Copy
rules/common+ your language-specific rules into~/.claude/rules/ecc/ - [ ] Configure Hook Profile: Set
ECC_HOOK_PROFILE=minimalfor low-context setups, orstrictfor maximum enforcement - [ ] Explore the Dashboard: Run
npm run dashboardto see all available agents and skills - [ ] Try the Planner Agent: Start with
/plan "Describe your project"to see agent delegation in action - [ ] Run a Security Scan: Execute
/security-scanon your project directory - [ ] Enable Continuous Learning: Activate
continuous-learning-v2to let your system improve over time - [ ] Optimize Costs: Review
cost-aware-llm-pipelinesettings for your budget
Looking Forward
With v2.0.0-rc.1, ECC has reached a significant milestone with its alpha Rust control-plane (ecc2/). This prototype introduces server-style commands (dashboard, start, sessions, status, stop, resume, daemon) and represents the future trajectory: moving from a CLI-driven plugin toward a proper daemon-based system.
The roadmap also includes:
- Billing Portal & Cost Controls: Built-in usage tracking and billing integration
- Expanded Media Tooling: Manim video creation, Remotion video workflows
- More Framework Support: NestJS patterns, expanded Codex/OpenCode surfaces
- Ecosystem Hardening: Ongoing AgentShield improvements and ECC Tools enhancements
For the full picture, visit the ECC Releases page and the official Shorthand Guide, Longform Guide, and Security Guide.
Conclusion
Everything Claude Code is not just another prompt library or configuration collection. At 178,000+ stars with active weekly commits, it has become the de facto optimization layer for AI coding agents. Whether you’re a solo developer wanting to ship faster, a team lead enforcing code quality, or a startup optimizing every dollar of API spend, ECC provides the structure, security, and skills that turn chaotic AI-assisted coding into a disciplined, productive engineering workflow.
Start with the minimal install, explore the dashboard, and let your agents learn from every session. The question isn’t whether you should use an AI coding assistant anymore — it’s whether you can afford to use one without ECC.
Related Articles: