210K+ starsFor Claude Code, Codex, Cursor, and OpenCode
Skills, agents, and security for your coding agent.
Pick a profile. Install the skills and agents your team needs. AgentShield scans every session. The GitHub App turns repo history into reusable defaults.
261 skills, 64 agents, and 84 commands in the OSS layer 102 security rules scan every agent session Works across Claude Code, Codex, Cursor, and OpenCode
Used by thousands of developers and engineers across various Fortune 500 teams· estimated from GitHub stars, forks, npm installs, and ecosystem downloads
Watch the demo · 1:45
Watch ECC analyze a repository, extract workflow patterns, and turn them into reusable skills and defaults
0
GitHub Stars
0
Security Rules
0
Contributors
0
npm Downloads/mo
Works across Claude Code, Codex, Cursor, and OpenCode
Claude Code
Codex
Cursor
OpenCode
[ THREE LAYERS ]
ECC is not one repo. It is a system with three layers.
The repo drives distribution, AgentShield provides protection, and ECC 2.0 is the operator layer that sits above individual harnesses.
Distribution layer
Open-source harness toolkit
The repo stays the front door. Skills, commands, hooks, adapters, demos, and install profiles keep ECC useful before anyone pays.
The ECC OSS repo stays MIT-licensed
Cross-harness coverage across Claude Code, Codex, OpenCode, Cursor, and more
Repo gravity and content distribution feed the rest of the system
Protection lives beside distribution, not behind it. Teams can audit configs locally, then add automation, policy packs, and enterprise reporting only where needed.
Open-source scanner for auditable trust
GitHub App automation for PR scanning and risky-context review
Enterprise path for reporting, governance, and custom rules
ECC 2.0 is shipped: a local-first control plane for observability, orchestration, session management, and cross-harness operations above the underlying tools.
Session and task visibility across multiple harnesses
Token optimization, operator review, and shared policy context
Open source builds trust. The GitHub App turns repo history into team guidance. ECC 2.0 is the operator layer above the harness.
The product story gets clearer when those three jobs are visible instead of collapsed into one blob.
[ THE LEARNING LOOP ]
Your agents get smarter every session. Your team stays in sync automatically.
Git history shows what changed. Session history shows how the work actually happened — the corrections, the failures, the fixes. ECC learns from both, prunes what stops paying rent, and keeps every teammate on the current version.
Learn beyond diffs
Session-history learning
Corrections, error-to-fix sequences, and repeated workflows become atomic instincts with confidence scoring. New instincts start unproven and earn trust by recurring across sessions.
Rule-based, inspectable extraction — no black-box learning
Confidence reinforcement across sessions, not one-shot guesses
Local ingest keeps raw transcripts on your machine
Anti-bloat
Auto-pruning and decay
Unpruned learning systems bloat until injected context hurts more than it helps. Idle instincts decay on a schedule and are removed once they cross the floor — with a reviewable plan before anything is deleted.
Idle instincts decay instead of living forever
Dry-run prune plans show what goes and why
Health metric: instincts that survive pruning while being used
Team sync
Central skill registry
GitHub is too clunky for non-developers and Notion cannot carry code. Publish skills centrally, and every seat converges on the current version at session start — install, update, and remove, enforced automatically.
Publish and update skills without touching git
Versioned with checksums, authorship, and revision history
Deprecate once centrally, removed everywhere on next sync
Opt-in usage insight closes the loop.
Teams choose what to share — nothing by default, aggregate counts, or per-skill usage. Never code, content, or transcripts.
[ GITHUB APP PRICING ]
Choose the GitHub App tier that matches the team surface
One install path. Start free on public repos, move to Pro for private repositories and active seats, then scope Enterprise when rollout and governance become the real job.
FreePublic repos
$0
/ month
Best for OSS maintainers and evaluation on public repos.
Free proves fit, Pro supports real teams, and Enterprise handles rollout.
[ THE DIFFERENCE ]
AI coding with ECC
See how ECC upgrades the same workflow without forcing a tool reset or hiding the open-source layer.
Without ECC
Your coding agent does not know your team's patterns
Manual test writing with inconsistent coverage
Security vulnerabilities slip through reviews
No shared coding standards across the team
Every session starts from scratch
VS
With ECC
ECC teaches Claude Code, Codex, OpenCode, and Cursor your exact conventions
TDD and verification workflows move testing earlier and make review expectations explicit
AgentShield catches config vulnerabilities
Shared skills and agents across the whole team
Continuous learning evolves with your codebase
[ SKILLS & TOOLS ]
Start with the skills and tools teams actually reuse
The GitHub App is the conversion surface, but these are the workflows that make the ECC ecosystem sticky: battle-tested skills, agents, security tools, and automation helpers you can adopt in minutes.
What you get after the first runEnough proof to decide whether to stay free on public repos, expand into private repos, or keep the OSS path local-first.
Reviewable PRSuggested skills and defaults arrive as normal code review instead of silent automation.
Repo-specific guidanceYour git history becomes reusable harness instructions your team can keep and refine.
Clear next stepStay free, move to private repo coverage, or send teammates to the OSS onboarding path.
Prefer local-only first? Jump to OSS install, pick a profile, and add the GitHub App later when repo automation matters.
Reviewable security for agent configs, hooks, MCP servers, and prompt surfaces before they become team defaults.
AgentShield
Scan CLAUDE.md, .cursorrules, agents.json, hooks, and MCP surfaces with the same open scanner you can later automate in pull request review. The value is clear scope, high-signal findings, and a credible path into policy packs and enterprise rollout.
Product, install, and rollout updates across the GitHub App, OSS layer, AgentShield, and ECC 2.0.
Jun 2026
ECC 2.0.0 stable — the agent harness operating system
261 skills, the orch-* orchestrator family, control-pane substrate with session adapters and MCP inventory, worktree-lifecycle service, single-connector MCP default policy, and the Discord community launch.
shipped
Mar 2026
GitHub App pricing and onboarding cleanup
Active-seat pricing, pooled usage, metered overage, and a cleaner GitHub App-first onboarding path for public repos, private repos, and enterprise rollout.
earlier this year
Mar 2026
Selective install and cross-harness packaging
Selective install profiles, universal package updates, and clearer OSS paths across Claude Code, Codex, Cursor, and OpenCode.
earlier this year
[ FAQ ]
Frequently Asked Questions
Quick answers to common questions about ECC Tools.
ECC Tools is the automated GitHub App that analyzes your repository's git history using AI and generates skill files. The ECC OSS repo is the open-source repository of pre-built skills, agents, hooks, and the continuous learning system. They're complementary: ECC Tools generates custom skills from your codebase, while the OSS repo provides battle-tested community configs you can use immediately.
Together they form the ECC system: open-source modules at the center, then additive layers for automation, security, and enterprise rollout.
The ECC OSS repo is completely free and MIT-licensed—you can copy, modify, and distribute any skills, agents, hooks, and modules without limits. The GitHub App free layer covers basic PR scanning, community skills, and public repos. For private repos and stronger automation, check the pricing page.
Paid plans are for private repos, advanced AgentShield scanning, team configs, and enterprise controls. Pro is $19 per seat for individuals and teams, and Enterprise is contact-only. The OSS install remains free.
The GitHub App requests read access to git history (commits, diffs, and branch info) and write access to create pull requests. It does not access secrets, environment variables, or any data outside the repository. All analysis runs through Claude AI and results are delivered as a PR for your review before anything is merged.
The fastest way is the universal installer: npm i -g ecc-universal. This installs all skills, agents, and hooks for Claude Code, Codex, OpenCode, Cursor, and related harness workflows. Alternatively, you can copy individual files from the GitHub repository into your project's .claude/ or compatible agent-config directory.
AgentShield is a security auditor for AI agent configurations like CLAUDE.md, .cursorrules, and agents.json. It uses an Opus 4.6-powered pipeline with three stages: a red team that crafts adversarial prompts, a blue team that validates guardrails, and an auditor that produces a scored security report. Run it with npx ecc-agentshield scan ./CLAUDE.md.
It is open source on purpose: teams can audit the scanner locally, then add automation and reporting on top through the broader ECC stack.
Absolutely! The ECC OSS repo is MIT-licensed and contributions are welcome. Fork the repository, add your skill or agent following the existing format, and open a pull request. The community reviews and tests contributions, and popular ones get featured in the showcase.
[ START WITH ECC ]
Turn the 210K+ stars ecosystem into a team workflow.
Start with the GitHub App for the fastest repo-level path, keep the OSS install where you want local control, and move into Pro or Enterprise only when private repos, policy, or rollout pressure become the blocker.
210K+ starsThe OSS front door keeps discovery, installs, and community trust flowing.
Free → $19/active seat → ContactOne GitHub App path from public-repo evaluation to rollout support.
102 AgentShield rulesSecurity and policy stay additive instead of forcing a workflow reset.
