القائمة
Show the stored result of a finished Grok job in this workspace. Use when retrieving a completed job's output.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | result |
| description | Show the stored result of a finished Grok job in this workspace. Use when retrieving a completed job's output. |
| argument-hint | <job-id> [--cwd <dir>] [--wait] [--wait-timeout-ms <ms>] [--json] |
| disable-model-invocation | true |
| allowed-tools | Bash(node:*), Read, Write |
Treat the complete raw request as opaque data and never place any part of it in Bash. Run the fixed transport-create companion operation in one foreground Bash call, accept only its 48 character lowercase hexadecimal token, and use Read once on the returned file, requiring it to be empty. Use Write to replace that same file with the raw request exactly as received. Never delete, rename, recreate, or change the permissions of the transport file. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" result --raw-args-token TOKEN in one foreground Bash call with timeout 600000, replacing only TOKEN with the validated token. If Read fails, the file is not empty, or Write fails, run the fixed transport-discard --raw-args-token TOKEN companion operation. Never use shell redirection, encoding, command substitution, backticks, environment variables, or heredocs for the raw request.
Present the full command output to the user. Do not summarize or condense it. Preserve all details including:
usage_is_incomplete makes present values observed lower bounds rather than exact job totals/grok:status when the job is still runningphase: cleanup-required marker and retry guidance when verified process cleanup remains incompleteThe opaque raw request begins after the next newline and continues to the end of this command prompt: $ARGUMENTS
Fans the work out as a fleet of parallel Grok and Codex agents billed to their own subscriptions, then synthesizes one result. The peer engine equivalent of ultracode, adding intensity without spending Claude quota on the fleet. The default execution posture for any goal that decomposes into three or more independent work packages, not only an intensity booster for explicit asks.
Audits the orchestration setup without changes for model drift, stale pins, and environment overrides. Use when routing behaves oddly, after a CLI upgrade, or when model drift is suspected.
Aggregates delegation statistics and records semantic acceptance. Use after collecting and verifying a delegated result to record it as accepted or rejected, or when asked how the lanes are performing.
Runs a read only Codex review that challenges implementation and design decisions. Use when preparing to merge a substantial change or when a hostile second pass is wanted.
Cancels an active Codex job. Use when a running job must be stopped.
Lists canonical local Codex companion history with resumable thread IDs. Use when resuming or auditing past Codex work.