Everything Claude Code is free and MIT-licensed, but a Pro tier exists at $19/seat/mo for private-repo support. Here is what the free core actually includes.
Everything Claude Code (ECC) is an open-source configuration collection that packages specialised AI agents, skills, commands, hooks and rules into one portable, version-controlled system. Created by independent developer Affaan Mustafa after winning an Anthropic hackathon — it is a community project, not an official Anthropic product — and aims to replace ad hoc prompting with structured, repeatable workflows for experienced development teams. For businesses standardising how multiple developers use Claude Code, it offers a ready-made starting point — but adopting any large third-party bundle means inheriting its engineering and security assumptions.
Quick Summary
Overall Rating 4.2/5 Best For Development teams standardising Claude Code usage across multiple engineers Pricing Core is free (MIT) - ECC Pro adds private-repo hosting from $19/seat/mo Free Plan Yes Ease of Use 3.5/5 Business Value 4.5/5
For teams that have moved past experimenting with AI coding assistants, the strategic question shifts from "can the model write code" to "how do we make its output consistent, reviewable and secure across an entire engineering organisation." Everything Claude Code addresses that second question by packaging an agent-first workflow — routing work to specialist agents, enforcing test-driven development and embedding security-first practices — into a single portable configuration. Rather than each developer inventing their own prompts, the bundle gives a team a shared baseline they can version-control and review like any other code. This matters most for organisations comparing Claude and other AI coding tools, where the difference between a good and a mediocre rollout is usually process, not the model itself.
Everything Claude Code sits in theaitoolsbox.com's AI Coding Tools category alongside other AI pair-programmers and coding agents.
Professional reality: A single hobbyist or solo developer who just wants Claude Code to write better code will likely find this bundle's setup and maintenance overhead excessive compared with configuring a handful of prompts directly.
Counted directly from the project repository rather than repeated from a press summary, the bundle currently packages 68 specialised agents, 292 skills and 94 slash commands - and the count changes often, since a single maintainer ships updates weekly across seven agent harnesses. A skill is not a general capability; each one is a narrow, named workflow the agent activates only when a task matches it.
A full breakdown by category, counted directly from the repository (not a rounded estimate):
| Category | Example skills |
|---|---|
| Framework & language-specific (46 of 292) | android-clean-architecture, angular-developer, bun-runtime, cisco-ios-patterns, clickhouse-io |
| Testing & QA (17 of 292) | agent-eval, agent-self-evaluation, ai-regression-testing, benchmark-methodology, benchmark-optimization-loop |
| Security & compliance (18 of 292) | agent-architecture-audit, automation-audit-ops, canary-watch, click-path-audit, customs-trade-compliance |
| Agent architecture & orchestration (21 of 292) | agent-harness-construction, agent-introspection-debugging, agent-payment-x402, agent-sort, agentic-engineering |
| Business operations (21 of 292) | article-writing, brand-discovery, brand-voice, carrier-relationship-management, competitive-platform-analysis |
| DevOps, infra & workflow (16 of 292) | cost-aware-llm-pipeline, deployment-patterns, dmux-workflows, docker-patterns, git-workflow |
| API, integration & MCP (9 of 292) | api-connector-builder, api-design, email-ops, github-ops, google-workspace-ops |
| Design & frontend (12 of 292) | accessibility, blender-motion-state-inspection, design-system, frontend-a11y, frontend-design-direction |
| Data & analytics (3 of 292) | dashboard-builder, data-scraper-agent, data-throughput-accelerator |
| Documentation & onboarding (7 of 292) | codebase-onboarding, documentation-lookup, ecc-guide, ecc-recipes, living-docs-governance |
| Engineering standards & patterns (8 of 292) | architecture-decision-records, backend-patterns, blueprint, coding-standards, contract-first |
These 11 categories account for 178 of the 292 skills. The remaining 114 span a long tail of narrow specialisations - homelab networking, healthcare compliance, investor materials, video and motion work among them - each too small individually to warrant its own row here. The project maintains the complete, current list in its own repository rather than in any third-party summary, including this one.
The 68 agents follow a similar pattern to the skills above - most are narrow specialists rather than general-purpose assistants, and the largest single cluster is language-specific code review:
| Agent category | Example agents |
|---|---|
| Language-specific code review (23 of 68) | code-reviewer, python-reviewer, typescript-reviewer, react-reviewer, rust-reviewer |
| Build-error resolvers (12 of 68) | build-error-resolver, go-build-resolver, java-build-resolver, react-build-resolver |
| Planning & architecture (10 of 68) | architect, planner, chief-of-staff, code-architect, network-architect |
| Testing & quality (9 of 68) | tdd-guide, e2e-runner, agent-evaluator, silent-failure-hunter, performance-optimizer |
| Open-source & docs (5 of 68) | opensource-packager, opensource-sanitizer, doc-updater, docs-lookup |
| Business & content (4 of 68) | marketing-agent, seo-specialist, comment-analyzer, conversation-analyzer |
For a broader look at AI coding tools beyond skill configurations, see our roundup of the best AI coding tools in 2026.
The bundle ships a set of specialised agents — reported in the dozens and varying by version — each scoped to a particular kind of task. Rather than one general-purpose assistant handling everything, work is routed to an agent with relevant context and constraints. This mirrors the agent-first approach also seen in tools like CrewAI.
Business outcome: more consistent, reviewable output because each task is handled by an agent with a defined scope.
ECC packages a substantial collection of skills — third-party reporting cites figures from roughly 135 to 183 depending on version — covering frameworks, languages and workflows. Skills give the assistant reusable, structured knowledge instead of one-off prompting.
Business outcome: less time re-explaining conventions, and more consistent results across a team.
The collection includes dozens of commands and hooks that trigger defined behaviour at specific points in a session. Hooks in particular let a team enforce steps — like running checks before a change is accepted — rather than trusting each developer to remember.
Business outcome: process compliance becomes structural instead of dependent on individual discipline.
ECC targets Claude Code, Cursor, Codex and OpenCode from the same repository, with install targets for additional harnesses added over time. For teams that use more than one assistant, this reduces the drift that comes from maintaining separate setups.
Business outcome: a single source of truth for AI workflow configuration across tools.
Because ECC is a repository rather than a set of settings buried in a UI, changes to the workflow can be reviewed, diffed and rolled back like code. This is the feature that makes it viable for teams rather than individuals.
Business outcome: workflow changes go through the same review discipline as the codebase itself.
The project ships security guidance and a documented security contact, and its README warns explicitly against installing from unofficial mirrors. This reflects an awareness that a widely-adopted configuration bundle is an attractive target.
Business outcome: a documented security posture to evaluate, rather than an implicit trust assumption.
Everything Claude Code is free and open-source under the MIT license. There is no paid tier for the core configuration bundle, which is distributed through the project's GitHub repository and published npm packages. The project website lists official install channels — the GitHub repository, the npm packages, the GitHub App, and the plugin slug — and warns that third-party re-uploads and unofficial mirrors are not maintained or reviewed and may contain malware. Because ECC is free, the real cost of adoption is not licence fees but the engineering time spent installing, evaluating and maintaining the configuration as it evolves. A commercial ECC Pro tier is confirmed live on the project's GitHub page: $19/seat/month for private-repo support via a hosted GitHub App, funding ongoing development of the free core. A separate Sponsor tier starts from $5/month for anyone who wants to fund the open-source project without needing the private-repo features.
| Plan | Price | What You Get |
|---|---|---|
| Open Source (MIT) Best Value | Free | Full configuration bundle via the official GitHub repository and published npm packages. |
| Official Install Channels | Free | Guided setup or native plugin commands, both installing the same plugin. |
| ECC Pro (GitHub App) | $19/seat/month ($190/year) | Private-repo support, funds ongoing development of the free core. |
| Sponsor | From $5/month | Funds the open-source project without needing private-repo features. |
Visit the official Everything Claude Code website to check the latest pricing and plans.
For the wider developer tooling landscape, see our guide to the best AI tools for developers in 2026.
A team of five to fifty developers can adopt ECC as a shared baseline, so agent routing, testing expectations and security rules are consistent rather than personal. This is the scenario where the bundle's overhead is most clearly justified.
Teams that want TDD and security checks to be structural rather than aspirational can use hooks and rules to make those steps part of the workflow. The trade-off is that the team must accept the maintainer's definition of those practices.
Agencies and consultancies that use Claude Code on some projects and Cursor or Codex on others benefit from one configuration repository. It reduces the per-project setup work that otherwise repeats on every engagement.
Teams still deciding how to formalise AI-assisted development can use ECC as a reference implementation — reading its structure is informative even if they later build their own. Compare this with broader developer tools before committing.
Read the official repository README and confirm you are installing only from verified channels — the GitHub repository, the published npm packages, or the plugin slug — never an unofficial mirror.
Choose either the guided setup or the native plugin commands; both install the same plugin, and the project advises against stacking a full manual install on top.
Run the installation in a single developer's environment first and review the agents, skills, hooks and rules it introduces before rolling it out to the team.
Commit the configuration to version control and establish a review process for updates, since the project changes frequently between versions.
For a development team that has already decided to standardise how it uses Claude Code, Everything Claude Code is worth evaluating seriously — it is free, actively maintained and solves a real problem in a structured way. The value is highest where multiple developers need a shared, reviewable baseline and where TDD and security-first practice need to be structural rather than optional. The value is lowest for a solo developer or hobbyist, for whom the setup and maintenance overhead outweighs the benefit of a large bundle. The main caveat is dependency risk: a fast-growing project maintained largely by one person should be evaluated as a dependency with a bus-factor question attached, not as a guaranteed long-term product. Treat the exact agent and skill counts as approximate, and review the security assumptions before adopting them wholesale.
Teams evaluating alternative agentic CLI tools should also see OpenCode for an open-source multi-model option.
| Decision Area | Everything Claude Code | When Another Option Wins |
|---|---|---|
| Best for | Teams standardising Claude Code usage across multiple developers | Cursor for developers who want an all-in-one AI-native editor rather than a configuration layer |
| Pricing | Free and open-source under MIT | GitHub Copilot for teams that want a paid, vendor-supported subscription with formal SLAs |
| Key feature | Portable, version-controlled agents, skills, commands, hooks and rules | Claude Code unconfigured for developers who prefer to build their own minimal setup |
| Ease of use | Guided setup and native plugin commands, but a large bundle to learn | A hand-rolled prompt library for solo developers who want zero overhead |
| Scaling | Strong for teams that need a shared, reviewable configuration | A vendor-supported platform when long-term support guarantees are a hard requirement |
Cursor is an AI-native code editor, while Everything Claude Code is a configuration layer that sits on top of harnesses including Claude Code, Cursor, Codex and OpenCode. The two are not direct substitutes — ECC can be used inside Cursor. Teams choosing between them are really choosing between an editor-centric workflow and a configuration-centric one. Cursor suits developers who want the AI deeply integrated into the editing surface itself.
Choose Everything Claude Code if: You want a portable, version-controlled workflow configuration that works across multiple harnesses. Choose Cursor if: You want an all-in-one AI-native editor rather than a configuration bundle layered on top of existing tools.
GitHub Copilot is a vendor-supported, subscription-based coding assistant with formal commercial backing, while ECC is a free, community-maintained configuration collection. Copilot offers the support guarantees and enterprise procurement path that a single-maintainer open-source project cannot. ECC offers deeper, more opinionated workflow structure and multi-harness portability. The trade-off is support certainty versus workflow depth.
Choose Everything Claude Code if: You want an opinionated, free, multi-harness workflow configuration you can review and version-control yourself. Choose GitHub Copilot if: You need vendor support guarantees, formal SLAs and an established enterprise procurement path.
Yes, the core is free. The full configuration bundle is open-source under the MIT license, distributed through the official GitHub repository and published npm packages, and stays free forever. An optional ECC Pro tier adds hosted private-repo support for $19 per seat per month, or $190 billed yearly - only needed if you want the GitHub App running against private repositories.
As counted directly from the project’s own GitHub repository, it currently packages 68 agents, 292 skills and 94 slash commands. The largest single cluster is language-specific code review and build-error resolution (roughly 35 of the 68 agents); the largest skill cluster is framework and language-specific work (46 of 292). Both counts change frequently since the project ships updates weekly, so treat any number - including this one - as accurate as of the date this review was checked, not fixed forever.
They span far more than coding. Skills are grouped into categories including agent architecture and orchestration, business operations (brand voice, competitive analysis, marketing), security and compliance, DevOps and infrastructure, design and frontend, and API/MCP integration, alongside the expected testing and framework-specific skills. Agents are more code-focused: the majority are per-language code reviewers and build-error resolvers, plus a smaller set for planning, testing and documentation. The full category breakdown with real example names is in the section above.
It is best used by development teams that want to standardise how Claude Code and other harnesses are used across multiple developers. It packages agents, skills, commands, hooks and rules into a version-controlled configuration, which suits organisations that need consistent, reviewable AI-assisted workflows rather than ad hoc prompting.
Unconfigured Claude Code gives a developer a capable assistant with no shared structure. ECC adds an agent-first workflow, a skills library, commands, hooks and rules on top. The trade-off is that ECC requires setup and ongoing maintenance, and adopting it means inheriting the maintainer's engineering and security assumptions rather than your own.
For a small team of developers already using Claude Code, it can be worth it because it is free and provides a shared baseline. For a solo developer or hobbyist, the setup and maintenance overhead of a large, frequently changing bundle usually outweighs the benefit. The deciding factor is whether more than one person needs the same workflow.
The exact agent and skill counts change frequently between versions, so any specific number should be treated as approximate. It is a fast-growing community project maintained largely by one person, which raises bus-factor and long-term-support questions. And adopting a full workflow configuration means trusting someone else's security and engineering assumptions.
Bottom Line: Everything Claude Code is a genuinely useful, free starting point for teams standardising AI-assisted development — but adopt it as a dependency you review, not as a product you can rely on indefinitely.
Last Reviewed: June 2026 | Reviewed by theaitoolsbox.com editorial team
Want the full breakdown of what is actually inside, category by category? Read Everything Claude Code Explained: 292 Skills, 68 Agents.
The core configuration bundle is free and open-source under the MIT license, distributed via the GitHub repository and published npm packages. No paid tier exists for the core free bundle itself.
A separate ECC Pro tier costs $19/seat/month (or $190/year) and is a hosted GitHub App that adds private-repo support while funding ongoing development of the free core. A separate Sponsor tier starts at $5/month for anyone who wants to fund the open-source project without needing private-repo features.
Only install via the official GitHub repository, npm packages, GitHub App, or the official plugin slug, because the project warns that third-party re-uploads and unofficial mirrors are not maintained or reviewed and may contain malware. Overall, it earned a 4.2/5 rating based on testing.
AI Coding Tools
Various plans available
Full configuration bundle via the official GitHub repository and published npm packages.
Private-repo support, funds ongoing development of the free core.
Funds the open-source project without needing private-repo features.
In-depth Cline review covering the open source AI coding agent, pricing, features, and who it's best for. See if it fits your …
In-depth Warp review covering the AI terminal, Agent CLI, and cloud software factories. Pricing, features, and who it's best for in 2026.
Gemini platform enables teams to build, scale, govern, and optimize enterprise-grade AI agents grounded in enterprise data, with 200+ models and MLOps …
Sourcegraph indexes entire codebases for AI-powered Deep Search, Code Search, Insights, and MCP server context, helping engineering teams understand, oversee, and evolve
Devin is an AI software engineer that automates large-scale code migrations, refactors, and ETL tasks. See how Nubank achieved 8x efficiency and …
Explore Google AI Studio pricing options, including free tier access and paid plans for developers. Compare costs for building with Gemini models …
v0 by Vercel lets you generate full-stack web apps with AI. Prompt, build, and publish live websites in seconds. Sync with GitHub, …
Bolt.new builds web components instantly with AI, ideal for developers and startups needing rapid UI.