Measuring Orchestration Cost

Use when asked whether delegating paid off, whether a run was expensive, or how much a fan-out cost in tokens — and before quoting any cost figure, saving, or percentage for agent work. Also use when writing a cost claim into a report, README, or commit message, or when a session hit a usage limit and you need to explain where the token budget went.

Writing & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add PapiScholz/symphony

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add PapiScholz/symphony --skill measuring-orchestration-cost
Manual install
git clone --depth 1 https://github.com/PapiScholz/symphony.git /tmp/symphony
mkdir -p ~/.claude/skills
cp -r /tmp/symphony/skills/measuring-orchestration-cost ~/.claude/skills/measuring-orchestration-cost

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Measuring Orchestration Cost

## Overview

Two questions get confused. *What did this run consume* is measurable from disk. *What would the alternative have cost* was never run and is a counterfactual. Never let the second borrow the authority of the first.

## First: does money even apply?

Before computing a single dollar, establish how the user is billed. Getting this wrong makes every figure that follows decorative.

| Billing | The right unit |
|---|---|
| Subscription (Pro, Max, Team seat) | **Not dollars.** The tokens are already paid for. Report token volume, the share that ran on premium models, and limits hit. |
| Per-token (API key, Bedrock, Vertex, Foundry, Console) | Dollars, priced from a rate card with a retrieval date. |

Claude Code's own docs: *"Claude Max and Pro subscribers have usage included in their subscription, so the session cost figure isn't relevant for billing purposes."* Quoting a dollar saving to a flat-rate subscriber is a number that appears on no bill.

Unknown billing? Ask, or lead with tokens — they are true either way.

## Two limits, not one

"Running out of context" and "running out of budget" are different failures and get conflated
constantly — in testing, 3/3 controls treated them as one resource.

| | What it is | What it is measured in | What fixes it |
|---|---|---|---|
Read the full skill on GitHub

Details

Skill name
measuring-orchestration-cost
Path
skills/measuring-orchestration-cost/SKILL.md
License
MIT
Repo updated
3 October 2026

FAQ

What does the Measuring Orchestration Cost skill do?

Use when asked whether delegating paid off, whether a run was expensive, or how much a fan-out cost in tokens — and before quoting any cost figure, saving, or percentage for agent work. Also use when writing a cost claim into a report, README, or commit message, or when a session hit a usage limit and you need to explain where the token budget went.

How do I install the Measuring Orchestration Cost skill?

Claude Code plugin: /plugin marketplace add PapiScholz/symphony. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Orchestrating Subagents

PapiScholz/symphony

Use when about to spawn one or more subagents, agent teams, or a workflow — a single delegated search, a parallel fan-out, or a repeated batch — and whenever choosing which model a delegated task runs on instead of letting it inherit yours. Also use when writing or editing a .claude/agents definition, when a delegated run hit a rate limit or cost more than expected, or when a subagent came back after far more or far fewer turns than the work warranted.

AI, LLMs & AgentsIn 1 list

When Not to Orchestrate

PapiScholz/symphony

Use when about to fan work out to parallel agents, when a user asks to "throw this at a bunch of agents" or parallelize for speed, and before splitting a refactor, rename, migration, or sweep across subagents. Also use when a delegated batch produced inconsistent or conflicting edits, or when deciding whether a task is worth delegating at all rather than doing it in one pass.

AI, LLMs & AgentsIn 1 list

Skill Seekers

Converts documentation websites into Claude Skills. Transform existing documentation into structured skills for Claude.

Writing & Content

Building Recommendation Systems

jeremylongshore/claude-code-plugins-plus-skills

This skill empowers Claude to construct recommendation systems using collaborative filtering, content-based filtering, or hybrid approaches. It analyzes user preferences, item features, and interaction data to generate personalized recommendations. Use this skill when the user requests to build a recommendation engine, needs help with collaborative filtering, wants to implement content-based filtering, or seeks to rank items based on relevance for a specific user or group of users. It is triggered by requests involving "recommendations", "collaborative filtering", "content-based filtering", "r

Writing & Content

Doc Hygiene

danybgoode/golden-frijoles

Keeps the always-read session-start docs (this project's AGENTS.md, Roadmap/WAYS-OF-WORKING.md, Roadmap/LEARNINGS.md, Roadmap/README.md poster) from re-bloating after the one-time de-noise sweep. Use when the product owner asks to "check doc hygiene", "measure LEARNINGS size", "is LEARNINGS bloated again", "run the doc hygiene report", or as the weekly Routine C hygiene pass. Runs scripts/doc-hygiene.mjs, reviews its flagged candidates against the source docs, and emits a dated advisory report. Never edits Roadmap docs — proposals only, the product owner or the builder hand-merges.

Writing & ContentIn 1 list

000 Jeremy Content Consistency Validator

jeremylongshore/claude-code-plugins-plus-skills

Validates messaging consistency across website, GitHub repositories, and local documentation. Generates comprehensive read-only discrepancy reports showing where messaging conflicts or inconsistencies exist. Activates when user mentions "consistency check", "validate documentation", "check for mixed messaging", "audit content consistency", or before updating internal paperwork.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.