MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses
Install Cco Tools
$ npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install egorfedorov/claude-context-optimizer cco-tools --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cco-tools .claude/skills/cco-tools && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cco-tools" agent skill from https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-tools into .claude/skills/cco-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cco-tools", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-toolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install egorfedorov/claude-context-optimizer cco-tools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cco-tools .agents/skills/cco-tools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cco-tools" agent skill from https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-tools into .agents/skills/cco-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cco-tools", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install egorfedorov/claude-context-optimizer cco-tools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cco-tools .cursor/skills/cco-tools && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cco-tools" agent skill from https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-tools into .cursor/skills/cco-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cco-tools", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/egorfedorov/claude-context-optimizer.git --path skills/cco-tools--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install egorfedorov/claude-context-optimizer cco-tools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cco-tools .gemini/skills/cco-tools && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cco-tools" agent skill from https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-tools into .gemini/skills/cco-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cco-tools", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install egorfedorov/claude-context-optimizer cco-toolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizer.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cco-tools .github/skills/cco-tools && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cco-tools" agent skill from https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-tools into .github/skills/cco-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cco-tools", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install egorfedorov/claude-context-optimizer cco-tools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/egorfedorov/claude-context-optimizer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cco-tools .opencode/skills/cco-tools && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cco-tools" agent skill from https://github.com/egorfedorov/claude-context-optimizer/tree/main/skills/cco-tools into .opencode/skills/cco-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cco-tools", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cco-tools- GitHub stars
- 114
- Token cost
- ~474 tokens
- SKILL.md length
- 236 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses
- Agent Workflows work in your project
- SKILL.md covers show (or no arguments) and reset
- Calls node
What it does
Cco Tools is an agent skill from egorfedorov/claude-context-optimizer. Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses
Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. It works with Model Context Protocol. The repository describes itself as: Claude Code plugin that tracks token usage, identifies wasted context, and saves 30-50% on API costs. Heatmaps, ROI reports, budget alerts, efficiency scores, git-aware… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/cco-tools”
Requirements
- Pre-approved tools (allowed-tools): Bash(node ${CLAUDE_PLUGIN_ROOT}/src/tool-costs.js:*)
What it can do on your machine
Read from SKILL.md and the folder at commit f6f20ee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(node ${CLAUDE_PLUGIN_ROOT}/src/tool-costs.js:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cco Tools loads about 474 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 236 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from egorfedorov/claude-context-optimizer at commit f6f20ee, republished under its MIT licence (© egorfedorov). 236 words, ~474 tokens.
Download SKILL.mdSave it as
.claude/skills/cco-tools/SKILL.md (or your agent's skills folder).- name
- cco-tools
- description
- Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses
- allowed-tools
- Bash(node ${CLAUDE_PLUGIN_ROOT}/src/tool-costs.js:*)
- license
- MIT
- argument-hint
- [show | reset]
CCO Tools — what your tools really cost
MCP and Agent token costs used to be constants picked once (mcp__* ≈ 200 in,
Agent ≈ 500). Real results vary by orders of magnitude — a "list all issues"
query and a one-row lookup are the same tool name and nowhere near the same
cost. On MCP-heavy sessions the budget meter was guessing at its biggest line
item.
CCO now measures every tool result and learns the average per tool name.
Run from the plugin root:
show (or no arguments)
node ${CLAUDE_PLUGIN_ROOT}/src/tool-costs.jsPrints the learned table: calls, average, worst case, and cumulative total per tool, sorted by total spend.
When reading it back to the user, the useful observations are:
- The top row by
totalis where their context budget actually goes. It is frequently an MCP server rather than file reads. - A row marked
·has fewer than 3 samples and is still using the built-in constant — its estimate isn't trustworthy yet. - A large gap between
avgandmaxmeans that tool is unpredictable; suggest narrowing its queries (filters, limits, pagination) rather than dropping it.
Pair with /cco-overhead mcp — that shows which servers are configured but
never called; this shows what the called ones actually cost.
reset
node ${CLAUDE_PLUGIN_ROOT}/src/tool-costs.js resetClears the learned table and returns every tool to its built-in constant. Useful after changing MCP servers or their configuration, when past measurements no longer describe the current setup. Confirm before running — the history isn't recoverable.
© egorfedorov, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/cco-tools of egorfedorov/claude-context-optimizer.
Open the folder on GitHubat commit f6f20ee
Compare with similar skills
Cco Tools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cco Tools this skillegorfedorov/claude-context-optimizer | 114 | — | ~474 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
MemPalace Memory Search
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
More from egorfedorov/claude-context-optimizer
All 13 skills in this repoSmart Loader
egorfedorov/claude-context-optimizer
Automatically suggests optimal files to preload based on the user's task description and historical context patterns.
Cco
egorfedorov/claude-context-optimizer
Context Control Center — one screen for budget, $ spent, tokens saved, waste, last prompt grade, the active task, and ready-to-run optimization actions
Cco Budget
egorfedorov/claude-context-optimizer
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5.5 default fallback, full 1M context at standard price)
Cco Config
egorfedorov/claude-context-optimizer
View and tune CCO's behavior thresholds — re-read warnings, cache staleness, prompt-coach length bands, and the /cco-pack budget cap
Cco Patterns
egorfedorov/claude-context-optimizer
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one
Cco Shield
egorfedorov/claude-context-optimizer
Show ContextShield status and waste protection stats; suggest or apply .contextignore rules from historical waste
Related
Works with
Categories
Questions about Cco Tools
What does Cco Tools do?
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses. Cco Tools is an agent skill from egorfedorov/claude-context-optimizer.
When should I use Cco Tools?
Cco Tools fits situations like: agent Workflows work in your project.
How do I install Cco Tools in Claude Code?
Run `npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a claude-code`. Or copy the skill folder (skills/cco-tools in egorfedorov/claude-context-optimizer) into .claude/skills/cco-tools in your project. Claude Code loads it when a task matches its description.
How do I install Cco Tools in Codex?
Run `npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a codex`. Or copy the skill folder (skills/cco-tools in egorfedorov/claude-context-optimizer) into .agents/skills/cco-tools in your project. Codex loads it when a task matches its description.
Can I use Cco Tools in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add egorfedorov/claude-context-optimizer --skill cco-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cco-tools, .gemini/skills/cco-tools, .github/skills/cco-tools and .opencode/skills/cco-tools in your project.
What does Cco Tools need to run?
Going by SKILL.md and its folder, Cco Tools needs the command-line tools its instructions call (node). Its frontmatter pre-approves these tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/src/tool-costs.js:*).
Does Cco Tools access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cco Tools safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cco Tools use?
Cco Tools is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cco Tools use?
About 474 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cco Tools?
Skills that share tags, products or a category with Cco Tools: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cco Tools?
egorfedorov (a GitHub user) maintains it in egorfedorov/claude-context-optimizer, which has 114 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 30, 2026.
Source: egorfedorov/claude-context-optimizer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.