Update to Token Weather

{
  "description": "Calculate numeric token headroom, task/output reserves and five future turns from supplied scalar estimates using the connected Token Weather budget MCP.",
  "included_files": [],
  "name": "plan-context-budget",
  "skill_md_contents": "---\nname: plan-context-budget\ndescription: Calculate numeric token headroom, task/output reserves and five future turns from supplied scalar estimates using the connected Token Weather budget MCP.\n---\n\n# Plan a token budget\n\nUse the connected `plan_context_budget` MCP tool for explicitly requested numeric\nbudget scenarios. Discover its current schema. If it is not connected, explain\nthat this package is prepared but no production endpoint is configured; do not\nclaim a tool call or deploy/install/connect it merely to answer a question.\n\nUse only numbers explicitly provided by the person for this calculation. A\nplatform/model name does not establish its context budget or current usage.\nReturn useful partial arithmetic when inputs are unknown; ask only for the\nmissing estimate needed for the requested result. Do not read local logs,\nscreens, account data, hidden conversation state or another chat for this tool.\n\nSupply `reference_limit_tokens`, `used_tokens`, `planned_increase_tokens` and\n`reserved_output_tokens` independently. Planned increase excludes the separate\noutput reserve. Zero must be explicit; absent/null remains unknown. Forecasting\nuses the optional scalar `growth_per_turn_tokens` supplied for future turns.\nDo not send recent-turn arrays, messages, IDs, paths, credentials or identity\nmaterial. The server accepts only scalar token counts and its fixed provenance\nenums. Tag assumptions in `sources`; supplied_measurement is a provenance label,\nnot a measurement verified by this service.\n\nExplain current and planned headroom/overage separately. The five-turn outlook\nstarts from current usage and excludes the one-off plan; it assumes the supplied\ngrowth rate continues. Weather uses reference cuts at 35%, 55%, 70% and 85%.\nReference crossing is not actual platform compaction, a spending cap or account\nquota. Cost and actual telemetry stay unknown.\n\nExample: reference 100000, usage 65000, task 20000 and reserve 5000 gives planned\nusage 90000 and headroom 10000. A separately supplied growth rate 10000 predicts\n75000/85000/95000/105000/115000, not real future telemetry.\n\nFor an explicitly requested local Codex reading or supplied event replay,\nfollow the separate token-weather skill and its privacy/access limits. Do not\nsend those records to the MCP. Read [privacy](../../docs/PRIVACY.md) when explaining\ndata handling. This plugin does not change models, settings, hooks or chats.\n"
}