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 notque/vexjoy-agent --skill session-handoffgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/session-handoff)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/session-handoff"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/session-handoff.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.01010 |
| Opus 5 | $0.00010 | $0.00505 |
| Sonnet 5 | $0.00004 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
session-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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Two modes sharing one state contract. HANDOFF packages current work so the next agent (or future session) resumes without re-discovery. PICKUP rehydrates from that package at session start. Pick the mode from intent: ending or pausing work = HANDOFF; starting on existing work = PICKUP.
Mode: HANDOFF
Produce a concise bullet package with these sections, in order. Use observed state and linked evidence. Label inherited results with their source; refresh mutable state before relying on it. Preserve every section, using “not applicable” when needed, without running irrelevant commands.
- Scope/status — the task in one line, finished vs. remaining work, blockers.
- Working tree —
git status -sbsummary; note local commits not yet pushed and the worktree path (git worktree list; do not infer it from a directory name). - Branch/PR — current branch, PR number/URL, CI status (
gh pr checks <num>when a PR exists). - Live processes — long-running jobs the next agent must know about: summarize
ps auxww | grep -E '<your-process>', plus a copy-paste attach or log-tail command (tail -f <logfile>,jobs -l). Redact secrets in command lines. - Tests/checks — commands, results, checked revision or file state, relevant configuration/environment, log paths, and remaining checks.
- Next steps — remaining actions in execution order, most urgent first.
- Risks/gotchas — flaky tests, feature flags, brittle areas, approvals still needed.
Gate: every live process has a copy-paste command; every pending step is ordered. Output format: bullet list, Dense-Complete — short enough to paste into a PR comment or session note.
Mode: PICKUP
Rehydrate in this order, then act.
- Read the handoff — the prior package and applicable repository instructions. Load named documents needed for the next action; a linked archive does not require a full reread.
- Repo state —
git status -sb; confirm branch, local commits, worktree path. - CI/PR —
gh pr view <num> --comments(derive the PR from the branch when unnumbered); note failing checks. - Processes — check for live jobs named in the handoff; attach or tail logs using its commands.
- Tests/checks — apply the evidence-reuse rules in
verification-before-completion. Check that inherited results cover the current files and relevant environment; rerun only invalidated or missing checks, plus required release/CI checks. - Plan — write the next 2–3 actions as bullets, then execute them.
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.
- 2d ago Changed · +1 lines d96ad4638443
- 3d ago First seen · 70 lines · 19 tokens per session scan A d8868ace160b
session-handoff is a skill published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 1,010 once invoked, about $0.0001 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-03.
Other skills, from other repositories
digital-brain
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
find-skills
Use when automatically discover, evaluate, and activate community skills when local skills don't cover user needs. Includes credibility scoring and safety checks for complete OpenClaw self-sufficiency.
autonomy-engine
Use when core autonomy protocol for AI agent operations. Defines how agents operate 24/7 without human prompts — monitoring all systems, generating revenue, managing team, escalating decisions, and growing. Use this skill to understand an autonomous operating system. Use when working with autonomy engine.
joko-proactive-agent
Use when proactive agent that detects signals and suggests actions with Slack notifications. Use when working with joko proactive agent.
notion
Read, create, and update Notion pages and databases via the Notion REST API.
closing-lite
A lightweight session-closing skill that saves important issues, lessons, and preferences to the agent’s persistent memory.