技能成本预测
- 作者仓库星标 3,406
- 作者仓库 claude-octopus
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @nyldn · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 读取环境变量
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
第 1 步:收集已完成阶段的成本
从`~/.claude-octopus/metrics/`或metrics-tracker.sh输出中读取成本数据。每个完成的阶段/步骤都应该有一个相关的成本条目。数据源(按优先级顺序): `~/.claude-octopus/metrics/session-*.jsonl` — 结构化的每阶段成本条目 `metrics-tracker.sh` 输出 — 旧会话的回退 HUD 累积成本计数器 — 最后的手段
第 2 步:计算每步的平均成本
计算所有已完成步骤的平均成本。公式: 示例:如果 3 步成本为 $0.30、$0.50、$0.40 → 平均值 = $1.20 / 3 = $0.40/步
第三步:项目剩余成本
将每步的平均成本乘以剩余步骤数。公式:按工作流类型划分的步骤计数:工作流 · 总步骤 · 示例阶段包含 · 4 · 发现、定义、开发、交付
第 4 步:在 HUD 中显示
设置 HUD/状态线显示的成本预测格式。标准显示: 格式规则: 所有美元金额精确到小数点后 2 位 预计总额以`~` 为前缀表示估算
第 5 步:预算上限警告
如果设置了 `OCTO_BUDGET_CEILING` 环境变量,请将预计总数与其进行比较并在溢出时发出警告。超出预算时显示: 低于预算时显示: 注意:`OCTO_BUDGET_CEILING` 是可选的。未设置时,不执行上限检查。
第 6 步:个人资料建议
如果预计总额相对于任务较高,建议切换到预算配置文件以降低成本。显示:预算配置文件 (`OCTO_PROFILE=budget`) 转向更便宜的型号并减少代理数量以最大限度地减少支出。
> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.
> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.
> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.
# Cost Projections Skill
## Overview
Projects remaining workflow cost based on per-phase averages from completed work. Displays cost data in the HUD/statusline and warns when projected totals exceed a configured budget ceiling.
**Minimum data requirement:** Needs **2+ completed steps** before projecting. With fewer than 2 data points, the average is unreliable — display actual spend only and skip projection.
## Step 1: Collect Completed Phase Costs
Read cost data from `~/.claude-octopus/metrics/` or from metrics-tracker.sh output. Each completed phase/step should have an associated cost entry.
```bash
# Read metrics from the session metrics directory
METRICS_DIR="$HOME/.claude-octopus/metrics"
SESSION_METRICS="$METRICS_DIR/session-$(date +%Y%m%d).jsonl"
# Each line contains: {"phase": "discover", "cost": 0.42, "tokens_in": 12000, "tokens_out": 3400, "timestamp": "..."}
# Sum costs from completed steps
completed_costs=$(jq -s '[.[].cost]' "$SESSION_METRICS")
completed_count=$(jq -s 'length' "$SESSION_METRICS")
total_spent=$(jq -s '[.[].cost] | add' "$SESSION_METRICS")
```
**Data sources (in priority order):**
1. `~/.claude-octopus/metrics/session-*.jsonl` — structured per-phase cost entries
2. `metrics-tracker.sh` output — fallback for legacy sessions
3. HUD accumulated cost counters — last resort
If fewer than 2 completed steps are available, display only actual spend:
```
💰 Spent: $0.42 (1 step complete — need 2+ for projection)
```
## Step 2: Compute Average Cost Per Step
Calculate the mean cost across all completed steps.
```bash
avg_cost=$(echo "$total_spent / $completed_count" | bc -l)
```
**Formula:**
```
avg_cost = total_cost / completed_steps
```
**Example:** If 3 steps cost $0.30, $0.50, $0.40 → avg = $1.20 / 3 = $0.40/step
## Step 3: Project Remaining Cost
Multiply the average cost per step by the number of remaining steps.
```bash
remaining_steps=$((total_steps - completed_count))
projected_remaining=$(echo "$avg_cost * $remaining_steps" | bc -l)
projected_total=$(echo "$total_spent + $projected_remaining" | bc -l)
```
**Formula:**
```
projected_remaining = avg_cost × remaining_steps
projected_total = total_spent + projected_remaining
```
**Step counts by workflow type:**
| Workflow | Total Steps | Example Phases |
|----------|-------------|----------------|
| embrace | 4 | Discover, Define, Develop, Deliver |
| research | 3-7 | Per-agent probe count |
| review | 3 | Fleet, Verifier, Synthesis |
| debate | 3 | Opening, Rebuttal, Synthesis |
## Step 4: Display in HUD
Format the cost projection for the HUD/statusline display.
**Standard display:**
```
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
```
**Format rules:**
- All dollar amounts to 2 decimal places
- Projected total prefixed with `~` to indicate estimate
- Use `💰` prefix for the cost line
- Show in a single compact line for statusline integration
**When insufficient data (< 2 steps):**
```
💰 Spent: $0.42 (need 2+ steps for projection)
```
**Integration:** This display line is emitted by the octopus-hud hook and rendered in the statusline alongside phase progress and provider status.
## Step 5: Budget Ceiling Warning
If the `OCTO_BUDGET_CEILING` environment variable is set, compare the projected total against it and warn on overrun.
```bash
if [[ -n "${OCTO_BUDGET_CEILING:-}" ]]; then
ceiling="$OCTO_BUDGET_CEILING"
if (( $(echo "$projected_total > $ceiling" | bc -l) )); then
overage=$(echo "$projected_total - $ceiling" | bc -l)
echo "⚠️ Budget ceiling: \$$ceiling — projected to exceed by \$$overage"
fi
fi
```
**Display when over budget:**
```
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
⚠️ Budget ceiling: $5.00 — projected to exceed by $1.00
```
**Display when within budget:**
```
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
✅ Within budget ceiling: $10.00
```
**Note:** `OCTO_BUDGET_CEILING` is optional. When unset, no ceiling check is performed.
## Step 6: Profile Suggestion
If the projected total is high relative to the task, suggest switching to the budget profile to reduce costs.
```bash
# Suggest budget profile when projected total exceeds $5.00 (configurable)
COST_THRESHOLD="${OCTO_COST_THRESHOLD:-5.00}"
if (( $(echo "$projected_total > $COST_THRESHOLD" | bc -l) )); then
echo "💡 Tip: Switch to OCTO_PROFILE=budget to reduce costs"
fi
```
**Display:**
```
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
💡 Tip: Switch to OCTO_PROFILE=budget to reduce costs
```
The budget profile (`OCTO_PROFILE=budget`) routes to cheaper models and reduces agent count to minimize spend.
## Complete Display Examples
**Normal — within budget, moderate cost:**
```
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
```
**Over budget ceiling:**
```
💰 Spent: $2.40 | Est. remaining: $3.60 | Total: ~$6.00
⚠️ Budget ceiling: $5.00 — projected to exceed by $1.00
💡 Tip: Switch to OCTO_PROFILE=budget to reduce costs
```
**Early in workflow (insufficient data):**
```
💰 Spent: $0.42 (need 2+ steps for projection)
```
**Low cost — no warnings:**
```
💰 Spent: $0.80 | Est. remaining: $0.80 | Total: ~$1.60
```
## Integration
### With octopus-hud hook
The cost projection line is rendered as part of the HUD statusline output, updated after each phase completes.
### With metrics-tracker.sh
Reads per-phase cost data written by the metrics tracker. Each completed phase logs cost, token counts, and provider details.
### With OCTO_PROFILE
When `OCTO_PROFILE=budget` is active, the projection accounts for reduced per-step costs from cheaper model routing.
## Error Handling
**No metrics directory:**
```
💰 Cost projection unavailable — no metrics data found
```
**Corrupted metrics data:**
Skip malformed entries and project from valid data only. If no valid entries remain, show unavailable message.
**Zero remaining steps:**
When all steps are complete, show final total only:
```
💰 Final cost: $4.80 (4 steps)
```
章节与文件索引
按说明文件中的顺序排列。
概述
第 1 步:收集已完成阶段的成本
第 2 步:计算每步的平均成本
第三步:项目剩余成本
第 4 步:在 HUD 中显示
文件/命令 -> /octo:* · skills/blocks/codex-host-adapter.md · ~/.claude-octopus/metrics/ · ~/.claude-octopus/metrics/session-*.jsonl · metrics-tracker.sh · OCTO_BUDGET_CEILING · OCTO_PROFILE=budget
内容校验值 -> 5a4d32f87b81
当前原文的自动摘译,尚未人工审校。
概述
根据已完成工作的每阶段平均值来预测剩余工作流程成本。在 HUD/状态行中显示成本数据,并在预计总额超出配置的预算上限时发出警告。最低数据要求:在投影之前需要完成 2 个以上的步骤。如果数据点少于 2 个,则平均值不可靠——仅显示实际支出并跳过预测。
第 4 步:在 HUD 中显示
设置 HUD/状态线显示的成本预测格式。标准显示: 格式规则: 所有美元金额精确至小数点后 2 位 预计总额以
~为前缀表示估算