← Orbit | Weekly Usage MaximizerCONTENT HISTORY
WHAT CHANGED
Update to Orbit | Weekly Usage Maximizer
Snapshot Nov 5, 2026 · 06:12 UTC · version 0.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Orbit | Weekly Usage Maximizer and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Start, view, or stop the Pace desktop usage tracker; compare the signed-in Codex account's remaining allowance with its full-period target and review recorded history. Requires local desktop execution. Not API billing or phone/cloud synchronization.",
"included_files": [],
"name": "pace",
"skill_md_contents": "---\r\nname: pace\r\ndescription: Start, view, or stop the Pace desktop usage tracker; compare the signed-in Codex account's remaining allowance with its full-period target and review recorded history. Requires local desktop execution. Not API billing or phone/cloud synchronization.\r\n---\r\n\r\n# Pace\r\n\r\nResolve `../../scripts/pace.mjs` relative to this skill folder. It is the plugin's bundled controller; run it with Node.js 22+ and one argument: `start`, `status`, or `stop`. Use a properly quoted absolute path. The script locates the user's Codex CLI and reads its signed-in ChatGPT account. Do not read credential files or ask for tokens.\r\n\r\nFor “start Pace”, setup, or opening the dashboard, run `start`. This starts a background local tracker that reads usage every minute until stopped or the computer shuts down. Explain that behavior briefly, then open its returned loopback URL in the available browser. If browser opening isn't available, provide the URL. Never substitute the publisher's private Pace website.\r\n\r\nFor a pacing or usage question, run `status` once. If stopped, say so; do not start ongoing tracking merely to answer a one-time question. If running with a fresh reading, use returned bucket values and reset time. Target remaining is `100 × clamp((reset − now)/(windowMinutes × 60000), 0, 1)`. Target used is 100 minus target remaining. Compare actual remaining minus target remaining in percentage points. The target always runs from 100% at the window's start to 0% at reset, independent of the current balance or optional reserve. Separate measured values from calculated targets. State source time and any stale/error status.\r\n\r\nFor “stop Pace”, run `stop`; this preserves recorded history. Do not remove histories unless the user asks. Updates record actual observations only, account-separated on the user's computer. Missing time is not reconstructed. History and preferences are not synchronized to phones or other computers.\r\n\r\nIf Node.js or Codex CLI is missing, explain the missing prerequisite. Follow the host's installation rules; do not silently install or sign in. If no ChatGPT account is signed in, ask the user to sign in through the normal Codex CLI flow, then try again. Never run a prompt, consume reset credits, change accounts, enable startup tasks, publish data, or alter the user's hosted website as part of this skill.\r\n\r\nThis is a local companion for personal account usage. Do not claim commercial integration approval or hosted access. On hosts without local execution, explain that the desktop plugin is required.\r\n"
}SHA-256 of public snapshot: f3551867396f6397fb05434771a537895c921fcc5f000ee7eeaad0d06ae865a0