Files
AgentHub/plugins/agenthub-cost-guard/commands/overspend.md
T
nntrivi2001 17d56d0e01 refactor!: rebrand CCAM to AgentHub
Clean break, no compatibility alias. Renames the product name, the CLI
binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` ->
`AGENTHUB_`), the Prometheus metric namespace (`ccam_*` ->
`agenthub_*`), the tmux session prefix (`ccam-lane-<id>` ->
`agenthub-lane-<id>`), the per-repo runtime profile directory
(`.ccam/profile` -> `.agenthub/profile`), the lanes state root
(`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled
plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash
commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` ->
`/agenthub:*`).

Because there is no alias, an existing install has to be updated by
hand: rename its `.ccam/profile` directory and any `CCAM_*` variables,
and reinstall the plugin under its new name.

Two other name families are deliberately left alone here, since they are
not just strings: the `Claude-Code-Monitor` repository/marketplace name,
and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard`
runtime directory, which holds the live database and needs a migration
rather than a rename.

Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across
tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).
2026-09-07 12:09:15 +07:00

945 B

description, argument-hint
description argument-hint
List the most expensive sessions pushing your spend up [top-N]

List the sessions driving Claude Code spend up — the top $ARGUMENTS most expensive (default top 10 if empty).

  1. Fetch a wide slice of sessions:

    curl -s "http://localhost:4820/api/sessions?limit=200"
    
  2. Sort the returned sessions by inline cost descending and take the top N.

  3. Print a table — rank, session id/name, model, started_at, metadata.turn_count, and cost (USD, 4 decimals). Below it:

    • Sum of the top N and what share of fleet spend they represent (sum top-N cost / sum of all cost).
    • Flag any Opus session with a low turn_count as a downshift candidate (point to the model-savings skill).

If the dashboard is unreachable, tell the user to start it with npm start from the repo root. Keep it to one table plus two summary lines. Read-only — do not modify anything.