cost-summarylisted

# Cost Summary ## Purpose Generate a human-readable cost summary from the yakos dispatch-log (`~/.yakos-state/dispatch-log*.ndjson`) over a configurable window. Designed for daily/weekly check-ins — operator runs the skill, gets a markdown summary, optionally posts to a Slack/Discord webhook. ## Scope - Reads the dispatch-log via `yakos cost --json`. - Formats a markdown summary with per-runtime, per-agent, and per-day breakdowns. - If `YAKOS_COST_WEBHOOK` is set in the operator's environment AND `--post` is passed, POSTs the summary to that webhook (Slack / Discord / Mattermost / generic JSON receiver). The webhook URL format is up to the operator; the skill emits a JSON body of `{"text": "<markdown>"}` which most chat receivers accept. - yakOS itself does NOT bundle a webhook secret; the operator supplies the URL via env var. ## When to use - Weekly / monthly cost review across runtimes. - After a heavy work week, to see which agents consumed the most. - For project hand-off documentation: include the cost summary so the next operator knows the burn rate. ## When NOT to use - For real-time per-call inspection — `tail -1 ~/.yakos-state/dispatch-log.ndjson | jq` is faster. - For accurate billing — yakOS estimates are best-effort. Real per-runtime token counts are emitted by the v0.6+ telemetry path for claude (and v0.6.x+ for codex/gemini); use the runtime's own billing dashboard for authoritative numbers. ## Automated pass 1. Read the runtime