cost-report

Compute token costs from memory/token-usage.csv using per-model rates from aeon.yml.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill cost-report-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cost-report
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/cost-report
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill cost-report-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes token usage across Aeon's workflows to quantify dollar spend, flag anomalies, and forecast future burn, enabling concrete cost optimizations.

Core Features & Use Cases

  • Automated cost aggregation: compute per-run costs from input/output tokens and cache usage.
  • Anomaly detection & forecasting: identify unusual spend and project 30-day burn.
  • Use Case: Run weekly reviews to steer optimization efforts and reduce token costs.

Quick Start

Generate a weekly cost report from memory/token-usage.csv to kick off cost-optimization discussions.

Frequently Asked Questions about cost-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate token usage costs from CSV memory data?

Token usage costs are calculated by reading memory/token-usage.csv, parsing numeric fields defensively, and computing cost per row using per-model rates from aeon.yml to produce a structured spend report.

What is the best way to detect spending anomalies in AI token usage?

The best way to detect spending anomalies is to analyze token usage memory data, which flags unusual spend patterns by computing per-run costs from input, output, and cache token data.

How do I forecast future token burn based on current usage?

Forecasting future token burn is achieved by analyzing historical token usage data to project a 30-day burn rate based on computed dollar spend from memory records.

Can I generate a weekly cost report for AI workflows without manual data entry?

Generating a weekly cost report without manual entry is possible by aggregating per-run costs from token usage data to produce a structured, publish-ready report for operational reviews.

Do I need an aeon.yml file to compute per-model pricing rates?

An aeon.yml file is required to compute per-model pricing rates, as the skill reads this configuration to apply accurate rates to input and output token counts from memory data.

Why does my token cost report show incorrect dollar amounts?

Incorrect dollar amounts in a token cost report typically result from malformed numeric fields in memory/token-usage.csv or misconfigured per-model rates in aeon.yml.