schedule-weekly-cost-analysis

Analyzes recorded token usage from weekly flow runs and produces prioritized cost-reduction recommendations.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-weekly-cost-analysis-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-weekly-cost-analysis
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-weekly-cost-analysis
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-weekly-cost-analysis-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted delivery flows consume tokens across models, stages, and sub-agents, and without a periodic review those costs accumulate unnoticed. This Skill reads the token usage already recorded by the bound delivery surface, identifies the top spending drivers, and turns them into concrete, prioritized cost-reduction actions. ## Core Features & Use Cases - Cost Data Aggregation: Collects flow runs in a configurable time window (default last 7 days) and aggregates total tokens, uncached tokens, per-model, per-stage, and sub-agent breakdowns. - Pattern Analysis: Detects the most expensive model and stage, compaction or truncation events, repeated prompts that could be cached, and runs restarted instead of handed off. - Prioritized Report: Outputs a structured weekly report with summary metrics, top cost-reduction tips, and repository-specific action items, with an optional full breakdown format. - Use Case: Run every Monday to review the previous week's flow runs, discover that a high-cost model handles low-complexity tasks, and get a checklist recommending a cheaper model tier for those agent files. ## Quick Start Run the weekly cost analysis for the last 7 days and show me the top cost-reduction tips from our recorded flow runs.

Frequently Asked Questions about schedule-weekly-cost-analysis

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

FAQPage Schema
How do I analyze token usage costs from AI flow runs?▼

Run this Skill with a time window such as last-7-days or an ISO date range. It calls list_runs and get_run on the bound delivery surface, aggregates token totals and breakdowns, and produces a report with prioritized cost-reduction tips.

How to reduce AI model costs in automated delivery pipelines?▼

The Skill identifies the most expensive model and stage, flags high-cost models used for low-complexity tasks, and detects runs restarted instead of handed off. It then recommends concrete actions such as switching agent files to cheaper model tiers.

What happens if no delivery surface is bound when running cost analysis?▼

The Skill skips the surface reporting calls, states this once, and continues with file artifacts as the source of truth. If no flow runs fall inside the window, the analysis is a no-op since it only reads recorded data.

Does weekly cost analysis modify repository files?▼

No, cost data is read-only and the Skill never modifies repository files on its own. Changes only happen if the user approves a follow-up action in Phase 4, such as invoking suggestion-review on a high-cost skill file.

What is the difference between summary and full output format?▼

The summary format shows only the top tips with headline metrics like total tokens and estimated cost. The full format appends per-model token and cost breakdown tables, all returned tips, and session-level or agent-level breakdowns when available.