メニュー
Check remaining subscription quota across providers (Claude, Codex) before routing or delegating token-heavy work, so a session sends bulk work to the model family with more headroom. Use at session start and before large delegations or fan-outs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and operate a durable, task-shaped HTML surface when a human needs to understand, inspect, edit, annotate, compare, decide, approve, or triage generated material with an agent. Use for visual review loops, decision sessions, media review, structured editors, reports, plans, batches, and other work that is clearer in an interactive surface than chat.
Run a documented grilling session in claudex with Claude leading the interview and the GPT/Codex-family grill-advisor challenging the opening design tree and auditing the final decisions. Use when the user wants Claude and Codex to stress-test a plan or design together while recording ADRs and domain terminology.
Compact the current conversation into a handoff document for another agent to pick up.
Watch a Quality Run Chapter execute in another session, read-only, and produce an evidence-first evaluation of how the agents behaved against the rules they were given. Use when a human wants a skill change, routing change, or orchestration change tested on a live Chapter and needs an independent record of what actually happened — not the Driver's own account of it.
Run /quality-loop under claudex with quota-aware Claude-spine and Codex-spine profiles. The selected family coordinates and implements while the other family supplies a persistent design advisor and fresh Correctness-vs-Design reviewer. Use for a substantial autonomous system build that needs cross-family scrutiny, explicit session boundaries, and resumable handoffs.
Turn an outcome, optional discovery brief, or existing GitHub Issue into an approved system design, autonomously implemented and adversarially reviewed semantic Chapters, and a human-readable System Story. Use when the user wants agents to build a substantial change while the human reviews architecture and behavior rather than every code diff, invokes /quality-loop, or resumes an active Quality Run.
| name | quota-axi |
| description | Check remaining subscription quota across providers (Claude, Codex) before routing or delegating token-heavy work, so a session sends bulk work to the model family with more headroom. Use at session start and before large delegations or fan-outs. |
You are running through CLIProxyAPI with two subscription backends — Claude (Anthropic OAuth) and Codex/GPT (ChatGPT OAuth). The scarce resource is quota, not dollars. Before committing token-heavy work to a family, check what's left.
Run the recommendation command immediately before choosing workers:
<skill-dir>/scripts/quota-axi recommend --task-shape bulk
Use fanout for several parallel workers and review for an independent review. The command
runs quota-axi --json, applies the policy below, and prints ROUTE, headroom, freshness,
the reason, and the exact next action. Follow NEXT. If FRESHNESS=stale, treat the route as
advisory and refresh authentication before a large irreversible fan-out.
(One-time: the user must run quota-axi --allow-keychain-prompt and approve the
macOS Keychain dialog before Claude quota is readable; Codex works without it.)
Each provider reports windows[] with percentRemaining and resetsAt. Treat
the lowest relevant window as the provider's headroom.
Apply these when choosing which model does the bulk (worker/executor) role. Keep the lead model as configured unless its family is critically low.
model-orchestration skill unchanged (Claude spine + GPT review layer).gpt-* workers and the GPT reviewer; run an
all-Claude spine (Fable/Sonnet/Haiku). Note the switch to the user.gpt-5.6-* and
lean on Codex; keep only light Claude usage.resetsAt.Always state, in one line, the emitted route and reason so the routing decision is visible.
ROUTE=stop; never guess its quota.