Burn-rate trend over time with optional drift-alert exit code. Bins session spend into buckets, surfaces window-over-window delta, and can exit 1 when latest bucket exceeds prior mean by a configurable %. Distinct from `cost-trend` (benchmark drift); this tracks PRODUCTION spend trajectory.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Burn-rate trend observability. The fourth leg of the cost-tracker forward-cost stack:
| Question | Skill |
|---|---|
| "Have we crossed a threshold?" (reactive) | cost-budget-check |
| "When will we cross a threshold?" (predictive) | cost-projection |
| "Could we have spent less?" (comparative) | cost-counterfactual |
| "Is daily burn ACCELERATING?" (trend) | cost-burn ← this |
Implementation: scripts/burn.mjs.
session-* records from cost-tracking namespace.--bucket duration windows (default 1d) over --lookback (default 14d).{n: sessions, spendUsd: sum(total_cost_usd)}.delta = latest.spendUsd - mean(prior non-empty buckets).--alert-on-acceleration-pct N is set: exit 1 when deltaPct > N.| Latest bucket spend | $0.500000 (1 sessions) |
| Prior bucket mean | $0.100000 (4 non-empty buckets) |
| **Delta (latest vs prior mean)** | **+$0.400000 (400.00%)** |
# | Window | Sessions | Spend
0 | 2026-06-15 14:16 → 2026-06-16 14:16 | 1 | $0.500000
1 | 2026-06-14 14:16 → 2026-06-15 14:16 | 0 | $0.000000
2 | 2026-06-13 14:16 → 2026-06-14 14:16 | 1 | $0.100000
3 | 2026-06-12 14:16 → 2026-06-13 14:16 | 1 | $0.100000
...
$ cost burn --bucket 1d --lookback 7d --alert-on-acceleration-pct 50 ⚠ ALERT: latest bucket $0.500000 is 400.0% above prior mean $0.100000 (threshold +50%) exit 1
$ cost burn --bucket 1d --lookback 7d --alert-on-acceleration-pct 500 ✓ latest bucket within +500% of prior mean (actual delta: 400.0%) — OK exit 0
# Fail the build if today's spend accelerated > 100% over the weekly mean
cost burn --bucket 1d --lookback 7d --alert-on-acceleration-pct 100 || alert-oncall
The alert is independent of budget — it triggers on rate ACCELERATION even when total spend is well under budget. Catches "we shipped a hot loop that burns 10× normal" before the budget alarm goes off.
cost-trend| Skill | Data source | Question |
|---|---|---|
cost-trend | docs/benchmarks/runs/*.json | "Is the benchmark drifting (win rate, latency)?" |
cost-burn | cost-tracking namespace | "Is production spend accelerating?" |
Both useful; they answer different questions on different data.
Infinity/null in JSON, marked new in the table. No alert fires (no baseline to compare against).--bucket > --lookback: hard error, exit 2.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add descriptions for new models from the HuggingFace router to chat-ui configuration. Use when new models are released on the router and need descriptions added to prod.yaml and dev.yaml. Triggers on requests like "add new model descriptions", "update models from router", "sync models", or when explicitly invoking /add-model-descriptions.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
日本語の概要は準備中です。原文の説明を表示しています。
Build or rebuild the ADR index + dependency graph by running scripts/import.mjs (handles v3-style and plugin-style ADR formats; one Bash call vs hundreds of MCP round-trips)
日本語の概要は準備中です。原文の説明を表示しています。
Reconcile the ADR index against a DELETED ADR file or relation line by dropping and rebuilding adr-patterns + adr-edges from scratch (scripts/reindex.mjs). Use when adr-index alone leaves stale rows behind.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes against accepted ADRs for compliance violations
日本語の概要は準備中です。原文の説明を表示しています。
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
日本語の概要は準備中です。原文の説明を表示しています。