Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/setrathexx/codex-engineering-workflow-pack/resume-supervised-runnpx skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill resume-supervised-rungit clone --depth 1 https://github.com/SetraTheXX/Codex-Engineering-Workflow-PackWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/resume-supervised-run)<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/resume-supervised-run"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/resume-supervised-run.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.00610 |
| Opus 5 | $0.00031 | $0.00305 |
| Sonnet 5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
resume-supervised-run scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Resume A Supervised Run
Read CEWP Core state before suggesting an action. This workflow may perform an explicitly requested non-model control, but it does not silently restart model work.
- If setup or capability readiness is in question, run
cewp doctor --jsonand present actionable remediation. - Run
cewp supervise status [run-id] --json. Omitting the id selects the latest supervised run. This command regeneratesprogress.mdfrom canonical state. - Summarize:
- run and checkpoint status;
- plan revision and source identity;
- completed evidence and attempts;
- latest targeted/full verification and failure classification;
- execution/worktree owner and backend;
- consumed and remaining allocations, protected reserve, thresholds, and absolute ceiling;
- managed usage as observed, estimated range with basis, and unavailable host usage as unknown;
- pause reason, blocker, and exact next safe action.
- For
paused-budget-safe,paused-budget-unverified, orpaused-host-limit, explain the trusted checkpoint and any partial isolated work separately. Never infer that the host limit cleared. - Apply a recovery control only with explicit user intent:
- resume:
cewp supervise resume <run-id> --yes --json; - add approved operations:
cewp supervise add-budget <run-id> --operations <count> --allocation <implementation|repair|reviewer|finalization> --yes --json; - revise an unstarted checkpoint:
cewp supervise revise <run-id> <changed fields> --json, then require fresh approval; - after a verified
budget-safepause, propose exactly one next bounded checkpoint with--goal,--scope,--verify, and--stop; CEWP seals prior evidence, andresumereturns to fresh proposal approval; - rollback isolated work:
cewp supervise rollback <run-id> --yes --json; - cancel or abandon:
cewp supervise cancel <run-id> --yes --jsonorcewp supervise abandon <run-id> --yes --json; - record a blocker:
cewp supervise block <run-id> --reason "<reason>" --json.
- resume:
- After a non-model control, run status again and stop before the next model operation. Direct the user to the checkpoint workflow when they choose to execute, retry, or review.
Do not rewrite progress.md, delete evidence, claim hidden token/credit data, clear a host limit without explicit resume, mutate the source repo, or bypass policy, scope, verification, reviewer PASS, or finalization gates.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 33 lines · 62 tokens per session scan A 78dbe8d0ca27
resume-supervised-run is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 610 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…