Receber por email
← Voltar para o catálogo

cost-report

Generate detailed cost reports with charts and breakdowns. Shows daily/weekly/monthly spend, per-tool costs, per-branch costs, and trends. Use when user says 'cost report', 'spending report', 'usage report', 'show costs', 'branch costs', or '/cost-report'.

34estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add Manavarya09/cost-guardian

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/cost-report/svg)](https://www.skillteca.com.br/skills/cost-report)

Skills relacionadas

Ver todas de Dados e Análise →

Alerta por categoria

Receba novas skills de Dados e Análise toda segunda

1 email curto, só com as skills novas de Dados e Análise. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Cost Report

Generate formatted cost reports with ASCII charts.

Commands

/cost-report or /cost-report session

Show current session report (enhanced with model breakdown and top expensive calls):

node "${CLAUDE_SKILL_DIR}/../../scripts/reporter.js" session "${CLAUDE_SESSION_ID}"

/cost-report daily

Show last 7 days with day-of-week labels, averages, and projected monthly:

node "${CLAUDE_SKILL_DIR}/../../scripts/reporter.js" daily 7

/cost-report weekly

Show last 4 weeks (28 days):

node "${CLAUDE_SKILL_DIR}/../../scripts/reporter.js" daily 28

/cost-report monthly

Show last 30 days:

node "${CLAUDE_SKILL_DIR}/../../scripts/reporter.js" daily 30

/cost-report branch

Show cost per git branch (last 30 days):

node "${CLAUDE_SKILL_DIR}/../../scripts/reporter.js" branch 30

/cost-report branch <days>

Show branch costs for a custom period:

node "${CLAUDE_SKILL_DIR}/../../scripts/reporter.js" branch <DAYS>

Display Rules

  • Show the ASCII output exactly as returned — do not reformat it
  • The box-drawing characters are intentional, preserve them
  • Add brief commentary only if there's a notable trend or budget concern
  • If no data exists yet, tell the user that tracking starts automatically
  • For branch reports, mention that branch tracking requires working in a git repo
Compartilhar X LinkedIn