goal_mode

Preserves restart-ready task state and resumes Codex work after quota recovery.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill goal-mode-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: goal_mode
Source: https://github.com/synthaicode/XRefKit/tree/main/skills/os/goal_mode
Command: npx skills add https://github.com/synthaicode/XRefKit --skill goal-mode-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When Codex usage quota hits 0%, in-progress work often loses its context, next actions, and unresolved items, forcing a costly reconstruction after the reset. This Skill keeps one goal continuable across quota exhaustion by recording a restart-ready continuation packet before waiting. ## Core Features & Use Cases - Continuation Packet Recording: Captures the goal, completed work, artifact paths, unresolved items, and the exact first action to take after recovery. - Explicit Wait Conditions: Records whether resumption depends on the next 5-hour reset, the weekly reset, or an unknown recovery point, without guessing reset times. - Drift-Checked Resume: Re-validates scope, branch state, and upstream changes before resuming substantive work after a long wait. - Use Case: A long-running Codex coding task exhausts usage mid-way. The Skill stops new work, writes a continuation packet with the exact next action, waits for the 5-hour reset, then resumes from the recorded state instead of recomputing the task. ## Quick Start Ask the agent to continue the current goal in goal mode so that when Codex usage reaches 0% it records a continuation packet and resumes after the next reset.

Frequently Asked Questions about goal_mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I continue Codex work after usage quota runs out?▼

Record a continuation packet containing the goal, completed work, artifact paths, unresolved items, and the exact next action before usage hits 0%. After the reset, resume from that packet instead of reconstructing the task from scratch.

What is a continuation packet in Codex goal mode?▼

A continuation packet is a minimal restart-ready record of the current goal, done and remaining work, artifact paths, unresolved items, and the first action after recovery. It lets a later session resume safely without rereading the whole task.

Does goal mode automatically resume Codex after the reset?▼

No. The Skill explicitly forbids claiming background wake-up or automatic restart unless a real scheduler, hook, or job queue exists. It only preserves state and wait conditions so resumption can happen safely.

What happens if Codex does not show the next reset time?▼

The wait condition is recorded as unknown rather than guessed. The Skill requires quota-state evidence to stay factual and source-based, and missing reset timing must never be invented.

Why check for drift before resuming a paused Codex task?▼

During a long wait, user instructions, branch state, or upstream artifacts may change. Resuming without a drift check can apply stale assumptions, so the Skill re-validates the boundary before continuing substantive work.