A report of the tokens and dollar cost used by dispatched agents, broken down by agent and run.

Checking spending after a review or orchestration run and investigating cost regressions.

It shows what an agent workflow actually costs and can reveal increases compared with earlier runs.

cost-report — Skill for Claude Code by bdfinst/agentic-dev-team

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add bdfinst/agentic-dev-team

Claude Code

/plugin install dev-team

Made for: Claude Code.

Or install dev-team, the plugin that ships this one along with the rest of its 98 skills, 54 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/cost-report/github.svg)](https://agentmods.dev/skills/bdfinst/agentic-dev-team/cost-report)

Your own site

<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/cost-report"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/cost-report/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/cost-report"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/cost-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,159 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00069	$0.02159
Opus 5.5	$0.00028	$0.00864
Sonnet 5.5	$0.00014	$0.00432
Haiku 4.5	$0.00007	$0.00216

Measured 1mo ago against content hash 6e5e5c3a35a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cost-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/dev-team/skills/cost-report/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cost Report (#102)

Role: worker. Reports runtime cost/token spend captured by the cost meter.

Token usage is not available to hooks, so the Stop/SubagentStop hook (hooks/cost_meter.py) records a per-session summary to metrics/cost-metering.jsonl by parsing the session transcript, converting tokens to dollars via knowledge/model-pricing.json. This skill reports that data.

Steps

Per-session breakdown. If the user passes --transcript <path> (or you know the current transcript path), run an exact per-agent report:
```
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/lib/cost_meter.py" report --transcript <path>
```
Otherwise show the most recently recorded session from the metrics log (prefer the migrated .claude/metrics/ location, falling back to the legacy bare metrics/ path for a project mid-transition):
```
log=".claude/metrics/cost-metering.jsonl"; [ -f "$log" ] || log="metrics/cost-metering.jsonl"
tail -n 1 "$log" | python3 -m json.tool
```

Regression check. Compare the latest session's total cost against the rolling mean of prior sessions (default tolerance +50%):

log=".claude/metrics/cost-metering.jsonl"; [ -f "$log" ] || log="metrics/cost-metering.jsonl"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/lib/cost_meter.py" regression \
  --log "$log" --tolerance 0.5

Report the per-model, per-thread (main/subagent), and per-agent-type tokens
- cost, the session total, and whether a cost regression was detected. Do not invent numbers — print exactly what the meter emits. If .claude/metrics/cost-metering.jsonl (or the legacy metrics/cost-metering.jsonl) is absent, tell the user the meter hasn't recorded a session yet (the hook records on turn end).
For a windowed cost-regression baseline (mean of only the N most recent prior sessions instead of all-time), pass --window N:
```
log=".claude/metrics/cost-metering.jsonl"; [ -f "$log" ] || log="metrics/cost-metering.jsonl"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/lib/cost_meter.py" regression \
  --log "$log" --tolerance 0.5 --window 10
```

Read the full file on GitHub · 179 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 179 lines · 69 tokens per session scan A 6e5e5c3a35a8

Subscribe to this mod's changes

cost-report is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 2,159 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Analytics and metrics

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.