codex-lightweight-scripts

name	codex-lightweight-scripts
description	Run or extend small dependency-free utility scripts for Codex workflows. Use when Codex needs a simple PowerShell or Bash helper for account checks, tiny automations, repeatable shell tasks, or lightweight environment operations, especially in Codex Desktop or shell-first environments where extra package installation is undesirable.

Codex Lightweight Scripts

Use bundled scripts for small shell-first tasks. Prefer running or extending an existing script before writing one from scratch.

Quick Start

• Prefer scripts/<task>/powershell/run.ps1 in Windows and Codex Desktop environments.
• Prefer scripts/<task>/bash/run.sh in Unix-like environments.
• Keep scripts dependency-free unless the user explicitly asks for another runtime.
• Read the target script before editing it so behavior stays aligned across shells.

Available Tasks

Check rate limit reset credits

Use one of these scripts to inspect the current Codex account's rate limit reset credits:

• scripts/get-rate-limit-reset-credits/powershell/run.ps1
• scripts/get-rate-limit-reset-credits/bash/run.sh

Both scripts read ~/.codex/auth.json and call the ChatGPT backend credits endpoint.

Sync this repository into the local skill directory

Use one of these scripts to install or refresh the skill from the repository source:

• scripts/install-skill/powershell/run.ps1
• scripts/install-skill/bash/run.sh

Add or Update a Script

When extending this skill:

1. Decide whether the task belongs in PowerShell, Bash, or both.
2. Prefer native shell features over Python, Node.js, jq, or other extra dependencies.
3. Keep behavior read-only by default unless the user explicitly asks for a mutating action.
4. Add clear failure messages for missing files, missing auth fields, or HTTP errors.
5. Put each action in its own scripts/<task>/ directory and keep shell entrypoints as run.ps1 and run.sh.
6. Update the repository README.md if you add or rename a user-facing script.

Behavior Rules

• Keep scripts small and directly inspectable.
• Preserve equivalent behavior when both PowerShell and Bash variants exist.
• Prefer explicit paths and obvious headers for network requests.
• Avoid storing secrets outside the existing Codex auth location unless the user asks for that design.