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 dayfinggg/openai-codex-agent-skills --skill handoffgit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/handoff)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/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/dayfinggg/openai-codex-agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/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.00053 | $0.00442 |
| Opus 5 | $0.00026 | $0.00221 |
| Sonnet 5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
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 3d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Follow the governing instructions and the user's requirements for communication, code style, authorization, and delegation. This skill supplies task-specific guidance, not permission to expand the task. Its workflow and output fields describe internal checks and relevant content, not a mandatory response layout or a progress report. When used within broader authorized work, continue that work through completion rather than stopping to deliver this skill's intermediate result.
Produce a continuation package that lets the receiver act without reconstructing the full conversation.
Capture current truth
State the objective, current status, completed work, files or systems touched, accepted decisions with reasons, governing constraints, and verification already performed. Link exact artifacts when available.
Preserve uncertainty
List unresolved questions, failed attempts that should not be repeated, assumptions that still need proof, and any user approval that remains required. Separate facts from recommendations.
Make continuation executable
Name the next concrete action, its inputs, expected result, and completion check. Include repository or environment state that the receiver must inspect before editing. Keep secrets and unnecessary raw logs out of the handoff.
For time-sensitive work, include the latest forecast or range, the owner of each blocking dependency, the next checkpoint, and the condition that triggers escalation or a fallback. Mark whether the forecast is evidence-based or still an assumption.
For an active incident, include evidence ownership, secure communication channel, current containment and recovery state, the next shift's objective, and explicit acknowledgement from the receiver. Do not place secrets or attacker-controlled content in the handoff.
Boundaries
Do not claim a handoff was delivered to another agent unless the corresponding message or transfer actually succeeded. A request only to create a handoff document does not authorize sending it, while an explicit request to send or transfer it does.
What ships with it
1 file 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.
- 3d ago Changed · +2 lines a2bf5092ccd6
- 5d ago Changed · +4 lines f370801b7817
- 10d ago First seen · 29 lines · 53 tokens per session scan A 1e9ed8277e4e
handoff is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (4 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 442 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
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
architecture-design
Use only when creating new registrable ML components that require Factory or Registry patterns.
results-analysis
This skill should be used when the user asks to "analyze experimental results", "run strict statistical analysis", "compare model performance", "generate scientific figures", "check significance", "do ablation analysis", or mentions interpreting experiment data with rigorous statistics and visualization. It focuses on…
review-response
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.