140K+ starsSkills, agents, and securityFor 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. 140K+ stars on GitHub. Start free, scale to enterprise.
181 skills, 47 agents, and 79 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
Security
AgentShield scanning
102 rules catch prompt injection, config drift, and guardrail gaps before they reach production. Open-source scanner with enterprise reporting path.
102 rules • 1282 tests • enterprise path
Automation
GitHub App workflow
Install on any repo. Comment /ecc-tools analyze. Review the PR that turns commit history into team-specific skills, standards, and checks.
Free → $19/active seat → Contact
Ecosystem
Skill catalog
181 skills, 47 agents, 79 commands. Pick a profile or build a custom install. Works across all supported harnesses.
Prefer the OSS path first? Use the selective install builder for a local profile, then add the GitHub App when repo-native review automation becomes worth it.
[ START HERE ]
Choose the path that fits how your team adopts ECC
ECC stays useful whether you start local-first, install the GitHub App on one repo, or need a more governed rollout. Pick the constraint you actually have today and grow from there.
Recommended for teams
Install on a real GitHub repo
Best when you want the fastest path from repo history to reusable team guidance, reviewable pull requests, and a clean path into private repos when the team is ready.
Public repos free · Pro and Enterprise later
Install the ECC Tools GitHub App on a repo or org.
Comment /ecc-tools analyze to generate repo-native skills and defaults.
Review the proposed PR before anything lands in the repo.
Best when you want the harness performance layer first across Claude Code, Codex, Cursor, or OpenCode before adding any GitHub automation. The OSS path stays first-class.
MIT modules · ecc-universal
Install ecc-universal to load skills, hooks, agents, and modules locally.
Adopt reusable commands like /tdd, /plan, and /security-review.
Add the GitHub App later when repo automation becomes useful.
Best when private repos, risk review, and team onboarding become the bottleneck. AgentShield, consulting, and the operator layer stay additive to the same system.
AgentShield · consulting · ECC 2.0 preview
Review the security model and AgentShield coverage before rollout.
Get rollout help for team standards, onboarding, and governance.
Preview the control-plane path for observability and policy operations.
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
The next product layer is 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
Preview entry point for the medium-term product roadmap
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.
[ TRUST AT A GLANCE ]
Built to stay reviewable, scoped, and additive
The GitHub App only makes sense if the boundaries stay obvious. ECC keeps the open-source core available, makes automation review-first, and stays narrow about what the app can touch.
No secret access
The GitHub App reads git history, diffs, and repo metadata so it can infer conventions. It does not read secrets, environment variables, or anything outside your repository.
Scoped to repo history + PR workflows
Review stays with your team
ECC opens a pull request with the proposed skills and guardrails. Your team can review, edit, merge, or close it like any other change before anything lands.
PR-first, no silent merges
Open-source core stays yours
The ECC OSS repo, known on GitHub as Everything Claude Code, remains MIT-licensed and installable locally with ecc-universal. Add GitHub App automation, AgentShield scanning, or rollout help only when you need them.
Public repos can start free. For private repos, advanced scanning, or enterprise controls, the paid plans stay additive to the same install flow.
[ FROM FIRST REPO TO TEAM ROLLOUT ]
ECC should feel useful on day one and more valuable as coordination gets harder.
The same system carries you from a single repo evaluation to shared harness memory and then into security, rollout, and governance. No rebuild. No tool reset.
01 · First repo
Turn repo history into a reviewable PR
Start on one public repo or stay local-first. ECC converts existing repo patterns into changes your team can inspect before merge.
Evaluate on one repository instead of redesigning the whole workflow
Review a normal pull request before defaults become policy
Keep the free public-repo path open while you assess fit
02 · Shared harness memory
Reuse the same skills across Claude Code, Codex, Cursor, and OpenCode
Once ECC understands the repo, the same defaults move back into day-to-day harness use instead of living in one engineer's local setup.
Keep ecc-universal useful for local-first contributors
Stop re-explaining project norms every new session
Carry repo defaults into daily coding workflows
03 · Rollout and guardrails
Add private repo coverage and rollout support only when needed
Upgrade when private repo access, deeper review, or org-wide rollout becomes the expensive part, not before.
Move from Free to Pro when private repos or active seats show up
Add AgentShield-backed review depth without losing the OSS core
Use Enterprise when governance or rollout becomes the blocker
[ PRODUCT SURFACES ]
Open source at the center, additive layers around it
Keep the OSS install, docs, demo, and modules at the center. Add GitHub automation, security, and rollout help only where your team actually feels the coordination pain.
GitHub App
ECC Tools GitHub App
The repo-native automation layer. Turn git history into reviewable guidance, keep proposed changes in PRs, and add deeper security or rollout support only when the team needs it.
Starts free for public repositories
Review every generated pull request before merge
Add AgentShield-backed checks and private repo coverage on paid plans
The front door most people start with. Skills, agents, commands, demos, and workflow docs you can copy, customize, and ship today. The repo is listed on GitHub as Everything Claude Code.
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.
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.
this month
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.
this month
Mar 2026
ECC 2.0 control-plane direction
Operator-surface work across session visibility, control-plane logging, workflow review, and the next layer above individual harness installs.
roadmap in motion
[ 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, published on GitHub as Everything Claude Code, 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 140K+ 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.
140K+ 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.
