goal-cost
Plan and run a Codex goal within a percentage limit measured against shared weekly usage. Use whenever the user asks to set, start, continue, resume, monitor, budget, or orchestrate a goal by weekly usage percentage, or asks for goal-cost controls. Record the starting meter and check it after each part. At halfway, review the remaining plan and adjust it when needed to complete the requested result within the percentage. Finish as soon as the work is complete. Treat the percentage limit as the final safety boundary.
Install
git clone https://github.com/sunflower-of-parchman/goal-cost /tmp/goal-cost && ln -s /tmp/goal-cost/skill ~/.claude/skills/goal-costFrom README
Goal Cost Use the percentage the user chooses as the working budget for completing the requested goal. The percentage sets the maximum movement allowed on the shared weekly meter. At halfway, compare the work completed with the full result still required. Adjust the plan when needed so the remaining work fits within the percentage. Create or continue a goal after the user asks for that action. Delegate work or create another task after the user asks for that action. Set the limit Get an explicit percentage before creating a goal with a limit. Ask one direct question when the percentage is missing. Treat 10% as 10 percentage points on the weekly meter. The phrase “10% of what remains” means 10 percent of the current remainder. Count every change in the shared account meter while the goal runs. Other Codex tasks can use the same allowance. Say so briefly when other tasks are active or likely. Keep the weekly percentage and native token budget separate.