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 markoblogo/abvx-agent-skills --skill happy-handoffgit clone --depth 1 https://github.com/markoblogo/abvx-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/markoblogo/abvx-agent-skills/happy-handoff)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/happy-handoff"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/happy-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/markoblogo/abvx-agent-skills/happy-handoff"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/happy-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.00038 | $0.00520 |
| Opus 5 | $0.00019 | $0.00260 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
happy-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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Happy Handoff
Resume the same Codex task in Happy after reaching a safe checkpoint. The handoff request authorizes starting Happy for the current task. It does not authorize commits, pushes, deployments, destructive actions, or unrelated changes.
Workflow
-
Finish the current tool call or other indivisible operation.
-
Preserve the workspace. Do not clean, stash, commit, or rewrite dirty work for the handoff.
-
Capture a compact checkpoint: completed work, current branch or directory, validation state, dirty files, active processes, and the next concrete step.
-
Require
CODEX_THREAD_ID, the current working directory, an authenticated Happy CLI, and the systemscriptcommand. If a prerequisite is unavailable, report the exact blocker instead of opening an unrelated session. -
As the final tool action, run:
python3 "${CODEX_HOME:-$HOME/.codex}/skills/happy-handoff/scripts/launch.py" -
Immediately return the checkpoint so it is stored in the task before Happy resumes it. Say that the handoff is scheduled and ask the user to open Happy on Android.
The launcher waits briefly, then starts happy codex --resume for the exact task in the same directory. Use --dry-run to validate prerequisites without scheduling a session.
Guardrails
- Never add
--yolo, bypass approval settings, or expand permissions. - Do not claim that Android received the task until the user observes it there.
- Do not enable voice or daemon autostart as part of a handoff.
- Starting the Happy daemon when it is needed is allowed by the handoff request.
- Windows is currently unsupported; macOS and Linux use different
scriptsyntax and are handled explicitly.
Output Shape
Report:
- checkpoint;
- task ID and workspace;
- launcher status:
dry-run,scheduled, orblocked; - next step in Happy;
- unverified boundary: Android receipt until observed.
Provenance
Original ABVX workflow around the MIT-licensed slopus/happy CLI. Happy is an external companion and is not bundled with this repository.
What ships with it
3 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.
- yesterday First seen · 52 lines · 38 tokens per session scan A 8afbc4775de9
happy-handoff is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 520 once invoked, about $0.0002 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-09-09.
Other skills, from other repositories
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
slides
A slide generator that creates PNG images for presentation decks, including simple backgrounds for spoken-video scripts and fuller layouts for standalone presentations.
typescript-project
Modern TypeScript project architecture guide for 2025. Use when creating new TS projects, setting up configurations, or designing project structure. Covers tech stack selection, layered architecture, and best practices.
idea-team
A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.
architecture-foundation
Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before…