skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
egorfedorov/claude-context-optimizer51 installs

cco-tools

Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses

How do I install this agent skill?

npx skills add https://github.com/egorfedorov/claude-context-optimizer --skill cco-tools
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill tracks and reports the token cost of other tools used by the agent. It allows the user to view a cost table or reset the tracked data by running a local Node.js script.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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.js

Prints 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 total is 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 avg and max means 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 reset

Clears 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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/egorfedorov/claude-context-optimizer/cco-tools">View cco-tools on skillZs</a>