agent-statuslisted

# /agent-status Displays a dashboard of the current conversation's health and token costs. ## Steps ### 1. Count messages Count your own responses in this conversation (each response ≈ 1 user message). This is an estimate — you cannot access exact counts. ### 2. Count tasks Run `view_tasklist` and count: - Total tasks - Completed tasks - In-progress tasks - Not started tasks ### 3. Estimate token costs Calculate based on these estimates: | Component | How to estimate | Tokens | |---|---|---| | **Conversation history** | responses × ~1,500 | variable | | **AGENTS.md** | always loaded | ~1,800 | | **Skill descriptions** | always loaded | ~4,100 | | **Matched rules** | count rules triggered this request × ~800 avg | variable | | **Matched skills** | count skills triggered this request × ~1,500 avg | variable | | **Platform overhead** | system prompt, tool schemas | ~15,000 | ### 3a. Read session cost ledger (measured, not estimated) Run `node scripts/cost/track.mjs` (silent — `TRACK_QUIET=1`) and parse the last record from `agents/cost-tracking/sessions.jsonl`. If the file does not exist (tracker never run for this project), skip this step and note `cost ledger: not initialised` in the dashboard. Extract from the latest record: - `total_usd` — dollars spent in the current session - `by_model[]` — per-tier (haiku / sonnet / opus) input / output / cache split - `budget.tier` — `under` / `50` / `75` / `90` / `100` (from `node scripts/cost/budget.mjs check`) Pricing so