Cc Cost Analysis
Analyze Claude Code usage costs from OpenTelemetry data — per-user spend, expensive sessions, context bloat, and model/token cost breakdowns — with a structured framework, ready-to-use query shapes, and cost-model formulas. Triggers on "analyze Claude Code costs", "break down the Claude Code bill", "find expensive sessions", "identify context bloat".
Install
/plugin marketplace add intercom/2x-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add intercom/2x-skills --skill cc-cost-analysisgit clone --depth 1 https://github.com/intercom/2x-skills.git /tmp/2x-skills
mkdir -p ~/.claude/skills
cp -r /tmp/2x-skills/plugins/claude-code-tools/skills/cc-cost-analysis ~/.claude/skills/cc-cost-analysisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Claude Code Cost Analysis A framework and ready-to-use query shapes for analyzing Claude Code usage costs across a team or org. ## Prerequisites: you need Claude Code telemetry Claude Code can export usage as OpenTelemetry metrics and events (`CLAUDE_CODE_ENABLE_TELEMETRY=1` plus an OTLP endpoint — see the Claude Code monitoring docs). Point that export at an observability backend (Honeycomb, Datadog, an OTLP collector into a warehouse, etc.). This skill analyzes that data. The example queries in `references/queries.md` are written for **Honeycomb** (environment/dataset names are placeholders — substitute wherever you send telemetry). The **analysis dimensions and cost formulas are backend-agnostic** — the same shapes translate to any store that has per-`api_request` rows with token counts, `cost_usd`, `model`, and `session.id`. A few attribute names in the examples (`user.email`, `speed`, `skill.name`, `normalized_file_path`) are enrichments that depend on your telemetry pipeline and Claude Code version — verify column names against your own data (`get_dataset_columns` or the equivalent) before relying on them. Numeric fields are sometimes stored as strings; cast with `FLOAT(...)` before aggregating (see the query examples). ## Analysis Dimensions Each dimension answers a different question. Run whichever are relevant — there is no required order, though broader dimensions provide context for narrower ones. | Dimension | Question Answered | Query Section |
Details
- Skill name
cc-cost-analysis- Repository
- intercom/2x-skills
- Path
plugins/claude-code-tools/skills/cc-cost-analysis/SKILL.md- License
- MIT
- Repo updated
- 11 November 2026
FAQ
What does the Cc Cost Analysis skill do?
Analyze Claude Code usage costs from OpenTelemetry data — per-user spend, expensive sessions, context bloat, and model/token cost breakdowns — with a structured framework, ready-to-use query shapes, and cost-model formulas. Triggers on "analyze Claude Code costs", "break down the Claude Code bill", "find expensive sessions", "identify context bloat".
How do I install the Cc Cost Analysis skill?
Claude Code plugin: /plugin marketplace add intercom/2x-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cc Cost Analysis popular?
It lives in intercom/2x-skills, which has 280 GitHub stars and 15 forks.
Related skills
Attach Github Assets
280intercom/2x-skills
Upload local files (screenshots, screen recordings, images, videos) to GitHub as user-attachment assets and return markdown-ready URLs for PR descriptions, issue bodies, or PR/issue comments.
Audit Memory
280intercom/2x-skills
Audit Claude's saved memories for claims that no longer hold true — verify each against current code, PRs and tickets, then archive the stale ones with your approval, and name the MCPs needed for anything unverifiable.
Create PR
280intercom/2x-skills
Open or update a GitHub pull request for the current branch — use when asked to create a PR, open a pull request, push and PR, or submit a PR.
Five Whys
280intercom/2x-skills
Run an evidence-grounded five-whys RCA: claims verified by fact-checker subagents, causal links stress-tested by a cynic subagent. For internal RCAs, post-mortems, "why did this happen". Not for customer-facing incident write-ups.
Sylph Setup Agent
220getnao/sylph
Set up an AI agent by validating her scope, schedule, and delivery channel. Run as `/sylph-setup-agent <agent-name>` or `/sylph-setup-agent all`.
Permissions Analyzer
280intercom/2x-skills
Vet a Claude Code permission allowlist against a GREEN/YELLOW/RED safety model and reduce permission prompts. Runs on top of the built-in /fewer-permission-prompts scan (and permission auto mode): filters proposed auto-allow commands through a GREEN/YELLOW/RED safety model — never auto-allowing interpreters or package-manager executors — before merging the safe ones into ~/.claude/settings.json. Also turns the proactive "reduce your prompts" suggestions off or on (disable/enable).
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.