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 skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill handoffgit 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/handoff)<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/handoff"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/handoff/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/handoff"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/handoff.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00903 |
| Opus 5.5 | $0.00023 | $0.00361 |
| Sonnet 5.5 | $0.00011 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
handoff 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Create a short, durable handoff that lets future Codex work resume without rebuilding context from the whole conversation.
Do not copy large PRDs, issues, diffs, or test logs into the handoff. Link or reference existing artifacts and capture only what is needed to continue.
Read First
Before writing, inspect:
docs/agents/handoff.mddocs/agents/issue-tracker.mddocs/agents/test-commands.md- current PRD or issue paths mentioned in the conversation
- changed files if available
- recent verification commands and outcomes
If setup docs are missing, propose this default:
docs/agents/handoff/
Use a timestamped file name such as:
docs/agents/handoff/YYYY-MM-DD-topic.md
Keep Windows paths quoted when showing commands or file locations.
What To Capture
Capture the current state of work:
- current goal,
- user-approved decisions,
- files changed or created,
- current implementation state,
- verification run and results,
- open questions,
- risks and gotchas,
- recommended next action.
Capture only enough detail for continuation.
What Not To Capture
Do not include:
- secrets, tokens, API keys, credentials, private personal data,
- full PRD or issue contents already stored elsewhere,
- long command logs,
- speculative future roadmap unrelated to the current work,
- unrelated repo findings,
- hidden chain-of-thought or private reasoning.
If sensitive data appeared in the conversation, redact it and mention that redaction occurred.
Workflow
1. Identify Purpose
Determine why the handoff is being created:
- end of session,
- pause before implementation,
- follow-up tomorrow,
- switch to testing,
- switch to another workflow skill,
- preserve decisions after a long conversation.
If the purpose is unclear, infer it from the latest user request and state the assumption.
2. Collect Existing Artifacts
Find and reference existing artifacts:
- PRDs,
- local issues,
- architecture notes,
- ADRs,
- test command docs,
- prior handoffs.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 184 lines · 57 tokens per session scan A a185a0a48289
handoff is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 903 once invoked, about $0.0002 per session on Opus 5.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
self-improvement
Captures lessons and promotes recurring patterns.
copilot-spaces
Use Copilot Spaces to provide project-specific context to conversations. Use this skill when users mention a "Copilot space", want to load context from a shared knowledge base, discover available spaces, or ask questions grounded in curated project documentation, code, and instructions.
context-checkpoint
Use when context usage needs checking or a compact/clear decision is due — a context warning or usage figure appears, the user asks whether to compact or clear, the session shows degradation (re-read files, repeated corrections, forgotten constraints), or a dev-workflow phase boundary is reached (step committed…
agent-continuity
Use when starting or resuming a non-trivial Codex/Cursor/Claude task, especially long-running design, coding, testing, handoff, or multi-agent work. Performs a lightweight new-session continuity check, finds or creates a task ledger, and prevents stale-file assumptions without forcing per-action checks.
dynamic-agent-context
Install and refresh dynamic learned context in any repo (.agent-context, AGENTS.md, learned-conventions.mdc). Use for coding, architecture code design, tests, refactors, code review, and bug fixes.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.