HomeClaude Code › Ecosystem
OverviewInstallCLI referencePricing & limitsAgent SDKSkills & pluginsGitHubWeb, desktop & IDEModelsErrorsOpen source?TutorialFor studentsQA automationvs Cursorvs Codex & OpenCodeSubagentsHooksMCPEcosystem中文指南
Last updated: September 22, 2026

The Claude Code ecosystem: routers, frameworks, plugins and the lists that track them

Claude Code's openness at the edges — environment variables, hooks, skills, a plugin marketplace, a status line hook — has grown a large ecosystem around a closed CLI. Most of it falls into five buckets: routing requests elsewhere, configuration frameworks, token-saving plugins, cosmetics, and lists. Here is what is actually in each.

TLDR

  • claude-code-router: a local proxy that sends different Claude Code requests to different models or providers by rule.
  • SuperClaude: a configuration framework adding commands, personas and workflows on top of Claude Code.
  • caveman: the viral plugin/skill that makes Claude answer tersely to cut output tokens.
  • Statusline: a settings.json hook that draws model, cost and context usage in the terminal.
  • everything-claude-code and awesome-claude-code: the collections that track the rest.

claude-code-router

musistudio/claude-code-router is a local control plane: Claude Code talks to it instead of the API, and it forwards each request to a provider chosen by rule — one model for background tasks, another for long context, another for "think" steps. Configuration lives in ~/.claude-code-router/config.json; you launch with ccr code. It is the answer to "can Claude Code use other models": yes, through a router, with the caveat that non-Claude models do not always handle Claude Code's tool schema well.

How it relates to this gateway: the router changes *which* model answers; the gateway changes *what the same model costs*. They compose — define the gateway as an Anthropic-type provider in the router's config with base URL https://aiprimetech.io and your key, and route the Claude tiers to it. If you only want Claude models cheaper, skip the router and set ANTHROPIC_BASE_URL directly; it is one variable and one fewer process.

SuperClaude

SuperClaude-Org/SuperClaude_Framework layers a set of slash commands, personas and workflow conventions over Claude Code — think of it as an opinionated CLAUDE.md plus command library, installed as a package. Useful if you want structure imposed on how you and your team drive the agent; unnecessary if you already have a good CLAUDE.md and a few skills. It is configuration, not a fork: the underlying CLI, billing and endpoint are unchanged.

caveman

JuliusBrussee/caveman became one of the most-starred projects in the ecosystem for a one-line idea — "why use many token when few token do trick": a skill that makes Claude respond in terse, article-free fragments, cutting output tokens substantially without changing what the agent does. It is installed as a skill or through the plugin marketplace; the README has the current command. Output tokens are the expensive side of every model, so on pay-as-you-go credits it pays for itself in a session; on a flat-rate plan it is a matter of taste.

Statusline

{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/statusline.sh"
  }
}

statusLine in settings.json runs a script that receives session JSON on stdin — model, working directory, context and cost figures — and prints one line Claude Code draws at the bottom of the terminal. Community scripts show the model, the percentage of context used, the session cost and git branch; the usage-tracking tools in the awesome lists ship ready-made ones. It is the cheapest way to notice a session drifting toward an expensive compaction.

Node.js for Claude Code

The npm package needs Node.js 18 or newer; node -v tells you what you have, and nvm is the sane way to keep a current version next to whatever your projects need. If you would rather not have Node at all, the native installer (curl -fsSL https://claude.ai/install.sh | bash, or the PowerShell line on Windows) ships a self-updating binary with no runtime. Most of the ecosystem above is Node-based too, so on a machine that runs Claude Code from npm nothing else is required.

The lists

What none of them change

Every project on this page runs on top of the same CLI and the same API call. Routers pick the model, frameworks shape the prompts, plugins trim the output, statuslines show the bill — and the bill itself is set by the endpoint. ANTHROPIC_BASE_URL=https://aiprimetech.io with a gateway key is the one change that lowers it for all of them at once: credits at 7.69× face value, or a flat-rate plan from $1.

PlanDurationPrice
Unlimited 1 Hour1 hour$1
Unlimited 24 Hours24 hours$10
Unlimited 1 Week1 week$49
Unlimited 15 Days15 days$89

All unlimited plans →

Frequently asked questions

What is claude-code-router?

A local proxy that routes Claude Code's requests to different models or providers by rule (background, think, long-context). It changes which model answers; a gateway changes what the model costs. They can be combined.

What is SuperClaude?

A configuration framework — commands, personas and workflows — layered over Claude Code. It does not modify the CLI or the billing.

What does the caveman plugin do?

Makes Claude answer in terse fragments to cut output tokens, installed as a skill or from the plugin marketplace.

Do I need Node.js for Claude Code?

For the npm install, Node 18+. The native installer needs no Node at all.

Run Claude Code on the gateway

Same models, two environment variables, credits at 7.69× face value — or a flat-rate unlimited plan.

Get an API key See unlimited plans

AI Prime Tech is an independent API gateway and is not affiliated with, endorsed by, or sponsored by Anthropic. “Claude” and “Claude Code” are trademarks of Anthropic. Claude Code features described here follow Anthropic’s public documentation at the time of writing and change frequently; prices and model lists on this page are read from this gateway’s live settings.

More Claude Code guides

Claude Code: the complete guideHow to install Claude CodeClaude Code CLI documentation: commands and flagsClaude Code pricing and limits, explainedThe Claude Code SDK, now the Claude Agent SDKClaude Code skills and pluginsClaude Code in GitHub: the App, the Action and @claudeDoes Claude Code have a web interface? Web, desktop and IDE explainedWhich model Claude Code uses, and how to change itClaude Code errors and how to fix themIs Claude Code open source?Claude Code tutorial: your first real sessionClaude Code for studentsHow to use Claude Code for QA automationClaude Code vs Cursor: which one, when — and how to run bothClaude Code vs Codex vs OpenCode: the terminal agents comparedClaude Code subagents: how they work, how to define them, and agent teamsClaude Code hooks: deterministic control over what the agent doesClaude Code MCP: connecting servers, scopes, remote MCP and real examplesClaude Code 怎么用:从安装到日常使用