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/jackfranklin/dotfiles/handoffnpx skills add jackfranklin/dotfiles --skill handoffgit clone --depth 1 https://github.com/jackfranklin/dotfilesWhat 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 | $0.00034 | $0.01186 |
| Opus 5 | $0.00017 | $0.00593 |
| Sonnet 5 | $0.00007 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff & Session Management
Use this skill when you want to summarize, save, or resume the state of your work. It supports three distinct operations based on the user's request:
- Save / Update Handoff: Write/update a progress summary file in
.jai/. - Search / List Handoffs: Scan
.jai/to find and resume work from a previous session. - Summarize: Generate a scannable conversation summary directly in the chat window.
1. Save / Update Handoff
Use when the user wants to "save progress", "update the handoff", or "write a handoff".
- Determine if this handoff represents a long-lived project plan (e.g., architecture, roadmap spanning multiple weeks/conversations) or a short-lived conversation handoff (capturing state for the next session). If the context makes this distinction unclear, ask the user for clarification.
- Generate a very short name for this task/plan if not already established (e.g.,
setup-handoff-skill). - Determine the target folder and file name format based on the category:
- Project Plan: Save to
.jai/plans/<short-name>.md. - Conversation Handoff: Save to
.jai/conversations/YYYY-MM-DD-<short-name>.md.
- Project Plan: Save to
- Check if a matching file already exists in the target subdirectory.
- If an existing file is found:
- Read its content to understand the current state.
- If the file is large (e.g., > 100 lines), ask the user for permission to append or if they prefer creating a new file.
- When updating, prefer appending new information to the relevant sections rather than replacing existing content.
- Prefix all updates with a timestamp (e.g.,
[2026-06-01 11:49]).
- If creating a new file or appending to an existing one, ensure the content covers:
- Summary: A single-line summary of the current state and goal.
- Original Goal: What was the user trying to achieve?
- Current Status: What has been completed so far?
- Next Steps: High-level objectives or next areas of focus.
- Key Decisions & Context: Non-obvious decisions or important context.
- Relevant Files: Files created, modified, or central to the task.
- Ensure the target directory exists before writing.
- Inform the user that the handoff or plan has been recorded/updated and provide the file path.
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 First seen · 73 lines · 34 tokens per session scan A 92af1c5c47cd
handoff is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 1,186 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…