How do I install the Rerun skill?

Run npx skillmds@latest add hashgraph-online-awesome-codex-plugins/rerun in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rerun safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rerun?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rerun free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

hashgraph-online (@hashgraph-online-awesome-codex-plugins) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rerun by hashgraph-online-awesome-codex-plugins

Name: Rerun
Author: hashgraph-online

Rerun

Launch a finished Codex Process Jobs record again as a new detached job using its validated persisted argv, working directory, and execution mode. Use only when the user explicitly asks or approves rerunning a specific completed, failed, or cancelled build, test, benchmark, inference run, data job, or repair.

File contents

Rerun Process Job

Resolve <plugin-root> two directories above this file and run:

node "<plugin-root>/scripts/job.mjs" rerun <job-id> [options] --json

Never search memory for CPJ work; use validated CPJ state.

The user-visible parent owns every CPJ rerun and completion. Never delegate local process execution, launch, waiting, monitoring, or CPJ ownership to a spawned subagent. A subagent can analyze independent material only.

Require a specific source job. If identity is unclear, use $status once to find it. Never reconstruct argv from displayed command text, logs, or model memory. The controller reads the private validated record, refuses active jobs, and creates a fresh job ID and logs with rerunOf lineage.

A rerun repeats the invocation, not the historical environment: files, dependencies, environment variables, credentials, devices, and external state may have changed. Mention a material change before launch; do not claim exact reproducibility.

Never rerun automatically from a completion notice. A direct user request authorizes an ordinary non-critical rerun. For a CRITICAL job, explain that the command may repeat repair, migration, firmware, or destructive effects and obtain explicit risk-aware approval immediately before adding --force.

Add --goal-mode only for an explicitly active Goal. Optional flags are --no-notify, --notify-user, and --no-notify-user. If the durable state directory is not writable in the current sandbox, request the same narrow controller escalation described by $start.

Treat a successful rerun as the same hard release boundary as $start: report the new job ID and its source job ID in no more than two short sentences. Say that a completion notification should appear when it finishes, then end the turn without status, tail, result, wait, sleep, or process monitoring. Do not narrate controller mechanics, persisted metadata, argv, cwd, or validation unless the user explicitly asks. If the controller refuses because the source remains active, its working directory disappeared, or legacy shell semantics cannot be preserved, report that refusal and do not improvise a replacement command.

---name: rerundescription: Launch a finished Codex Process Jobs record again as a new detached job using its validated persisted argv, working directory, and execution mode. Use only when the user explicitly asks or approves rerunning a specific completed, failed, or cancelled build, test, benchmark, inference run, data job, or repair.---# Rerun Process JobResolve `<plugin-root>` two directories above this file and run:```textnode "<plugin-root>/scripts/job.mjs" rerun <job-id> [options] --json```Never search memory for CPJ work; use validated CPJ state.The user-visible parent owns every CPJ rerun and completion. Never delegatelocal process execution, launch, waiting, monitoring, or CPJ ownership to aspawned subagent. A subagent can analyze independent material only.Require a specific source job. If identity is unclear, use `$status` once tofind it. Never reconstruct argv from displayed command text, logs, or modelmemory. The controller reads the private validated record, refuses active jobs,and creates a fresh job ID and logs with `rerunOf` lineage.A rerun repeats the invocation, not the historical environment: files,dependencies, environment variables, credentials, devices, and external statemay have changed. Mention a material change before launch; do not claim exactreproducibility.Never rerun automatically from a completion notice. A direct user requestauthorizes an ordinary non-critical rerun. For a `CRITICAL` job, explain thatthe command may repeat repair, migration, firmware, or destructive effects andobtain explicit risk-aware approval immediately before adding `--force`.Add `--goal-mode` only for an explicitly active Goal. Optional flags are`--no-notify`, `--notify-user`, and `--no-notify-user`. If the durable statedirectory is not writable in the current sandbox, request the same narrowcontroller escalation described by `$start`.Treat a successful rerun as the same hard release boundary as `$start`: reportthe new job ID and its source job ID in no more than two short sentences. Saythat a completion notification should appear when it finishes, then end theturn without status, tail, result, wait, sleep, or process monitoring. Do notnarrate controller mechanics, persisted metadata, argv, cwd, or validationunless the user explicitly asks.If the controller refuses because the source remains active, its workingdirectory disappeared, or legacy shell semantics cannot be preserved, reportthat refusal and do not improvise a replacement command.

Frequently asked questions